cloudposse / terraform-aws-ssm-patch-manager

Terraform module to provision AWS SSM Patch Manager maintenance window tasks, targets, patch baseline, patch groups and an s3 bucket for storing patch task logs
https://cloudposse.com/accelerate
Apache License 2.0
25 stars 17 forks source link

chore(deps): update terraform cloudposse/s3-bucket/aws to v4.2.0 #46

Closed renovate[bot] closed 4 months ago

renovate[bot] commented 7 months ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
cloudposse/s3-bucket/aws (source) module minor 4.0.1 -> 4.2.0

Release Notes

cloudposse/terraform-aws-s3-bucket (cloudposse/s3-bucket/aws) ### [`v4.2.0`](https://togithub.com/cloudposse/terraform-aws-s3-bucket/releases/tag/4.2.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-bucket/compare/4.1.0...4.2.0)
Added IP-based statement in bucket policy @​soya-miyoshi (#​216) ##### what - Allows users to specify a list of source IP addresses from which access to the S3 bucket is allowed. - Adds dynamic statement that uses the NotIpAddress condition to deny access from any IP address not listed in the `source_ip_allow_list` variable. ##### why Use cases: - Restricting access to specific physical locations, such as an office or home network ##### references
### [`v4.1.0`](https://togithub.com/cloudposse/terraform-aws-s3-bucket/releases/tag/4.1.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-s3-bucket/compare/4.0.1...4.1.0) ##### 🚀 Enhancements
fix: use for_each instead of count in aws_s3_bucket_logging @​wadhah101 (#​212) ##### what Replaced the count with a for_each inside `aws_s3_bucket_logging.default` there's no point in the try since the type is clearly defined as list ##### why When the `bucket_name` within `logging` attribute is dynamically defined, like in the case of referencing a bucket created by terraform for logging ```hcl logging = [ { bucket_name = module.logging_bucket.bucket_id prefix = "data/" } ] ``` we get this error Screenshot 2024-02-05 at 12 50 30 For each can work better in this case and will solve the previous error ##### references
##### 🤖 Automatic Updates
Update README.md and docs @​cloudpossebot (#​214) ##### 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
Update README.md and docs @​cloudpossebot (#​213) ##### 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
Update README.md and docs @​cloudpossebot (#​209) ##### 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

Configuration

📅 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.

renovate[bot] commented 7 months ago

Edited/Blocked Notification

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.

mergify[bot] commented 6 months ago

/terratest

mergify[bot] commented 4 months ago

💥 This pull request now has conflicts. Could you fix it @renovate[bot]? 🙏

mergify[bot] commented 4 months ago

This automated PR was closed due to merge conflicts.

renovate[bot] commented 4 months ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (4.2.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.