Releases: DNXLabs/terraform-aws-ecr
Releases · DNXLabs/terraform-aws-ecr
2.3.2
2.3.1
What's Changed
- Add scan on push, ecr lifecycle and kms optional by @lgothelipe in #18
New Contributors
- @lgothelipe made their first contribution in #18
Full Changelog: 2.3.0...2.3.1
2.3.0
2.2.0
What's Changed
- Adding AWS Lambda cross account deploy policy. Feature requested by @Elcio-Nakashima-Digitra on issue: #9
New Contributors
- @Elcio-Nakashima-Digitra made their first contribution in #16
Full Changelog: 2.1.0...2.2.0
2.1.0
What's Changed
- Added output values by @jrpradojr in #15
New Contributors
- @jrpradojr made their first contribution in #15
**Full Changelog: 2.0.2...2.1.0
2.0.2
2.0.1
2.0.0
1.0.1
1.0.0
What's Changed
- Enable KMS encryption and capability of using customer-managed key by @lzrocha in #10
⚠️ BREAKING CHANGE⚠️
This may destroy and recreate ECR repositories that have been created with previous module releases.
Now, ECR repositories will be encrypted with KMS keys stored in AWS Key Management Service (AWS KMS) by default instead of the Amazon S3-managed encryption at rest. When you use AWS KMS to encrypt your data, you can either use the default AWS managed key, which is managed by Amazon ECR, or enable an AWS customer-managed key.
New Contributors
- @caiovfernandes made their first contribution in #6
- @lzrocha made their first contribution in #10
Full Changelog: 0.3.2...1.0.0