Releases: schollii/terraform-aws-multi-stack-backends
Releases · schollii/terraform-aws-multi-stack-backends
fix iam policy generation regression
docs
typos etc
Cleanup and improve
- Resolve deprecation warnings, provide script to facilitate upgrade since this required new AWS resources
- cleanup API:
- Make access control IAM policies generation on-demand only
- Require that provider be inherited
- Module argument renamed
- No default tags or bucket name
- Improve docs
- Various other: created script for upgrade, created script for renaming buckets, start of unit tests
0.6.1
One lock table and improved iam policies
This version breaks backwards compatibility:
- one dynamodb table is sufficient (there is no advantage to one table per stack since the backend lock mechanism uses the backend key as lock key, rather than the dyname table name) -- ie one table can have multiple locks.
- IAM policy names changed to accomodate better breakdown of policies, and provide policy for whole stacks and individual modules
To update your backend states:
- remove all the
backend.tf
files produced by this module - run
terraform init
in each folder that had thebackend.tf
, to move the state back to local - run
terraform apply
on this module to regenerate allbackend.tf
- run
terraform init
in each folder that has a newbackend.tf
, to move the state back to S3
Docs improved
v0.5.2 Use path-independent key
First release to registry
This is the first release of terraform-aws-multi-stack-backends
module to hashicorp's terraform registry. It is fully functional but API should be treated as alpha: there may be changes to variable names and outputs, resource names etc. Ensure you pin to a specific version and if you upgrade, verify if any state manipulation will be required and raise an issue if you need support to handle that.