Skip to content

Releases: cloudposse/terraform-aws-ecr

v0.35.0

22 Nov 22:35
0472d64
Compare
Choose a tag to compare
adding force_delete @pcartas (#101)

Hi! im adding "force_delete" parameter, is implemented in aws 4.22.0 for an easier delete of the ecr

references

https://registry.terraform.io/providers/hashicorp/aws/4.22.0/docs/resources/ecr_repository

git.io->cloudposse.tools update @dylanbannon (#95)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

  • DEV-143

v0.34.0

22 Apr 22:25
56d7d3a
Compare
Choose a tag to compare
Fix aws provider v4 warnings @bwmetcalf (#93)

what

  • Replace deprecated parameters in aws v4

why

  • Make module compatible with v4

references

v0.33.0

21 Mar 18:31
58ca804
Compare
Choose a tag to compare
feat: Cross account ECR for lambda functions @dsme94 (#88)

what

  • With the introduction of cross-account ECR for lambda functions, I have put together the necessary code to allow for this functionality

why

  • Cross-account ECR is a feature many would use as it doesn't require you to duplicate your ECR repositories in the same account where the lambda function resides saving money

references

https://aws.amazon.com/blogs/compute/introducing-cross-account-amazon-ecr-access-for-aws-lambda/

v0.32.3

21 Aug 03:04
d4ee3b9
Compare
Choose a tag to compare

🤖 Automatic Updates

Update context.tf @cloudpossebot (#83)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.32.2

07 Feb 23:02
5385b7f
Compare
Choose a tag to compare

🤖 Automatic Updates

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#78)

what

  • update context.tf to v0.24.1
  • minimum required Terraform version bumped to 0.13.0
  • readme updated, Bridgecrew compliance badges added

why

  • It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
  • we have dropped support for Terraform 0.12
  • To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.32.1

05 Feb 03:06
39306f6
Compare
Choose a tag to compare

🤖 Automatic Updates

Update context.tf @cloudpossebot (#75)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.32.0

03 Feb 21:04
9ddc91d
Compare
Choose a tag to compare
minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#77)

what

  • update context.tf to v0.23.0
  • minimum required Terraform version bumped to 0.13.0
  • readme updated, Bridgecrew compliance badges added

why

  • It allows for setting the letter case of tag names and labels
  • we have dropped support for Terraform 0.12
  • To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.31.1

03 Feb 04:04
394c3a0
Compare
Choose a tag to compare

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#76)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.31.0

26 Jan 03:49
1c026ee
Compare
Choose a tag to compare
Bc compliance @maximmi (#74)

what

  • BridgeCrew compliance checks fix
  • readme updated
  • workflows updated
  • default behaviour changed: image_tag_mutability now IMMUTABLE by default
  • default behaviour changed: scan_images_on_push enabled by default

why

  • To be able to position our modules as standards compliant
  • stay in sync with code
  • to stay in sync with all repos
  • To comply BridgeCrew check

references

v0.30.0

23 Jan 15:27
21b94b4
Compare
Choose a tag to compare
Terraform 0.14 upgrade @maximmi (#72)

what

  • Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

  • Support Terraform 0.14