Releases: cloudposse/terraform-aws-ecr
Releases · cloudposse/terraform-aws-ecr
0.25.0
0.24.0: Use correct variable for multiple images (#59)
What
- Fixes one of the example projects
Why
- Examples allow consumers to copy / pasta and quickly get up and running with the module -- We want them working!
0.23.0: TF13: Need v0.17.0 of terraform-null-label (#61)
0.22.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#60)
## What 1. Update Version Pinning for Terraform to support 0.13 ## Why 1. This is a relatively minor update that the CloudPosse module already likely supports. 1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.
0.21.0: Add support for environment input/label (#57)
what
- Added support for the environment attribute that has been added to terraform-null-label
why
- Because we need to bring this up to speed!
0.20.0: Allow protecting images with specified tags (#56)
what
- Allow protecting images with a given set of tag names
why
- At Transcend, we tag images with
dev,staging, andprodfor deployments in addition to their SHA tags. We want to expire images, but not those actively is use.
references
- aws/containers-roadmap#637
- https://docs.aws.amazon.com/AmazonECR/latest/userguide/lifecycle_policy_examples.html
Note: This change is fully backwards compatible
0.19.0: support terraform 0.13 for for_each on modules #52
0.18.0: Allow disabling lifecycle hooks (#53)
what
Allow disabling lifecycle hooks across all created repos
why
Sometimes it's required to keep all images
