Terraform/Ansible/etc Defaults

[mickmcgrath13]

Similar to how helm allows specification of _default, can we do the same with Terraform?

Options

• Terraform multiple var files? (something to this effect: terraform apply -auto-approve -f $DEFAULT_VARS_FILE -f $ENV_VARS_FILE)
  • how does it handle the same keys/vars in multiple files?
• Terragrunt
• yaml-based stuff:
  • ytt
  • python terraform module

[ConnorGraham]

I'm interested in expanding this to not only include hosting var files in the _default environment, but also arbitrary .tf or yaml files to allow common terraform or ansible logic to not be duplicated across environments.

This could be accomplished using an rsync operation, but we'd be forfeiting merging functionality in this case.

[mickmcgrath13]

Let's chat about this in the next strategery topics meeting. I want to make sure it's clear how the current _default pattern works (for helm specifically) and how we've done arbitrary helm files (a la ytt) for halyard

[mickmcgrath13]

per file extension, we can have a default-merger that decides how files are merged from default to the deployed environment

i.e.

• yaml files: ytt
• .sh/.bash/etc: skip/replace/duplicate&rename (rsync?)
• terraform: skip/replace/duplicate&rename (rsync?)

maybe in bitops.config.yaml, we could have a copy section like:

terraform:
  copy:
    - extension: .tf
      operaton: rsync

[ConnorGraham]

Expected behaviour for file-mergers documented https://bitovi.github.io/bitops/default-environment/#file-mergers-todo

[PhillypHenning]

BitOps V2 version - #177