Closed renovate[bot] closed 7 months ago
/terratest
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
/terratest
This pull request now has conflicts. Could you fix it @renovate[bot]? 🙏
This automated PR has been closed due to merge conflicts.
Because you closed this PR without merging, Renovate will ignore this update (0.41.0
). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps
array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
This PR contains the following updates:
0.34.0
->0.41.0
Release Notes
cloudposse/terraform-aws-ecr (cloudposse/ecr/aws)
### [`v0.41.0`](https://togithub.com/cloudposse/terraform-aws-ecr/releases/tag/0.41.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-ecr/compare/0.40.1...0.41.0)Allow to use ECR replication @dmitrijn (#103)
- Allow to use ECR replication - https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ecr_replication_configuration Closes [https://github.com/cloudposse/terraform-aws-ecr/issues/99](https://togithub.com/cloudposse/terraform-aws-ecr/issues/99)Allow cache though enabled repositories to fetch image from upstream @mfuhrmeisterDM (#117)
#### what Add a principal list (`principals_pull_though_access`) which are allowed to use specific repositories as pull through cache (import images from upstream). This holds for repositories where one of the strings in `prefixes_pull_through_repositories` is a prefix of the repository name. #### why We are using `ecr-public` pull through cache and we want also new images to be downloaded automatically to the cache. Allowed principals for respective repos can use it with the newly introduced variables.Update README.md and docs @cloudpossebot (#116)
#### 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 templatesUpdate README.md and docs @cloudpossebot (#115)
#### 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 templatesUpdate README.md and docs @cloudpossebot (#114)
#### 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 templatesfeat: support scan_type @dudymas (#113)
#### what - add `scanning_configuration` as child module #### why - support `scan_type` settings - should be deployed as a per-account global, rather than per-ecr-repo #### Notes - fixes [#90](https://togithub.com/cloudposse/terraform-aws-ecr/issues/90)feat: add organizations as readonly access @dragosmc (#106)
#### what - Add the ability to have organizations as trustees (read-only) for the ECR repository #### why - As described in [#82](https://togithub.com/cloudposse/terraform-aws-ecr/issues/82) , it's sometimes useful to allow an entire organization to consume images from a centralized repository #### references - closes [#82](https://togithub.com/cloudposse/terraform-aws-ecr/issues/82)fix: cleans up principals lambda logic to separate policy doc @Gowiem (#105)
#### what - Clean up of the logic surrounding the `var.principals_lambda` policies #### why - When this was originally implemented it was copy / pastad across multiple policy docs, which isn't necessary and creates a bunch of bloat. #### references - Discovered in [#98](https://togithub.com/cloudposse/terraform-aws-ecr/issues/98) - Originally introduced in [#88](https://togithub.com/cloudposse/terraform-aws-ecr/issues/88)add optional policy allowing push access @kpankonen (#98)
#### what * adds the ability to give push-only access to the repository #### why * full access was more than we wanted in our situation (CI pushing images to the repo) so we added a `principals_push_access` to give push-only access. #### references * policy is based on [this](https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-policy-examples.html#IAM_allow_other_accounts) AWS docSync github @max-lobur (#104)
Sync github from the templateadding 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_repositorygit.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-143Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.