Hierarchical imports. New stacks config format. Generic Terraform backend @aknysh (#11)
what
- Use hierarchical imports
- Use new stacks config format
- Add generic Terraform backend config
- Simplify
why
-
Hierarchical imports - support
importup to five level deep (so we can, for example, import environment globals into a stack, which in turn can import globals for the entire solution) -
Use new stacks config format - all stack config files use the same schema. No special config files, they are all the same and can be arbitrary named. All Terraform and helmfile vars, commands, and backends are defined in separate sections in any of the config files or imported config files (no pollution of Terraform variables with provided but not declared variables, which will be an error in TF 0.14). All sections in the config files and imported config files are merged together into configs consumed by the relevant modules in the CLI
-
Add generic Terraform backend config - the ability to specify many different Terraform backends (e.g.
s3,remote,vault) and select a particular one per component, stage, environment, or the entire solution