v0.5.0

Update CLI for Terraform state backend @aknysh (#7)

what

• Update CLI for Terraform state backend

why

• Move the backend config logic from the variant files into YAML configuration
• Separate the backend configs from Terraform configs - do not pollute Terraform vars with not-related variables
• Make terraform-backend.variant completely generic - it will work with any backends (e.g. s3, remote) and is completely configuration driven

v0.4.0

Update to `stacks`. Add `import` to all configs. Remove hardcoded settings. Add Terraform S3 backend generation @aknysh (#6)

what

• Update to stacks (instead of environment/stage)
• Update to components (instead of projects)
• Add import to all configs
• Remove hardcoded settings
• Add Terraform S3 backend generation
• Simplify

why

• Use stacks instead of environment/stage to define configurations - this will allow arbitrary naming the stacks and not tying them to env/stage, as well as separation of stacks for the same environment/stage into different files (e.g. terraform config in one file, helmfiles config in another), or separation of stacks by AWS resources
• Add import to YAML stack configs - allow automatically importing global-globals and stack-globals into each configuration
• Remove hardcoded settings - make the CLI generic (no hardcoded namespaces, regions, IAM roles, etc.)
• Add (and simplify) the CLI commands to generate Terraform S3 backend configs for each Terraform component

v0.3.0

Update to support reference architectures @aknysh (#5)

what

• Update to support reference architectures

why

• Rename opsctl to atmos
• Rename projects/ to components/
• Add vendor CLI for synching reference architecture components
• Add terraform-backend CLI to generate Terraform S3 backends for Terraform components

v0.2.1

Allow (ignored) standard options for terraform clean @Nuru (#4)

what

• Allow terraform clean to take --stage and --environment options, even though they will be ignored

why

• Some scripts and tools provide those options for all Terraform commands that operate on a project, so it is convenient to allow them to provide the options to terraform clean even if they will be ignored, rather than raise an error about unknown options

0.2.0 Rename resources and update README

what

• Rename resources and update README

why

• Rename resources and update README after the repo name changed

0.1.0 Initial implementation

what

• Initial implementation of variants CLI cloud automation tool
• Add README
• Add example

why

• Create a CLI tool and provide usage example for

  • Provisioning Terraform projects
  • Deploying helm charts to Kubernetes clusters using helmfiles
  • Executing helm commands on Kubernetes clusters
  • Provisioning istio on Kubernetes clusters using [istio operator (https://istio.io/latest/blog/2019/introducing-istio-operator/) and helmfile
  • Combining various commands into workflows to execute many commands sequentially in just one step
  • ... and many more