-
-
Notifications
You must be signed in to change notification settings - Fork 331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add field create_aws_s3_bucket_public_access_block
to variable runner_worker_cache
#1105
Conversation
…ner_worker_cache` Some organizations may disallow configuring block public access settings on individual S3 buckets. For example, the organization may use account level configuration to block public access on all buckets. To support this, we add the field `create_aws_s3_bucket_public_access_block` to the `runner_worker_cache` variable. We add `count` to the `aws_s3_bucket_public_access_block` resource to control its creation and use the `moved` keyword to ensure that existing instances of this resource are not recreated due to this change.
Hey @KevinSnyderCodes! 👋 Thank you for your contribution to the project. Please refer to the contribution rules for a quick overview of the process. Make sure that this PR clearly explains:
With submitting this PR you confirm that you hold the rights of the code added and agree that it will published under this LICENSE. The following ChatOps commands are supported:
Simply add a comment with the command in the first line. If you need to pass more information, separate it with a blank line from the command. This message was generated automatically. You are welcome to improve it. |
create_aws_s3_bucket_public_access_block
to variable runner_worker_cache
create_aws_s3_bucket_public_access_block
to variable runner_worker_cache
create_aws_s3_bucket_public_access_block
to variable runner_worker_cache
create_aws_s3_bucket_public_access_block
to variable runner_worker_cache
…c_access_block_to_variable_runner_worker_cache
Did some quick tests in my environment. Looks good to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for improving this module.
…ock_to_variable_runner_worker_cache' of https://github.com/KevinSnyderCodes/terraform-aws-gitlab-runner into feature/add_field_create_aws_s3_bucket_public_access_block_to_variable_runner_worker_cache
🤖 I have created a release *beep* *boop* --- ## [7.5.0](7.4.0...7.5.0) (2024-04-11) ### Features * add field `create_aws_s3_bucket_public_access_block` to variable `runner_worker_cache` ([#1105](#1105)) ([aa93e76](aa93e76)) ### Bug Fixes * do not deregister GitLab tokens which are still in use ([#1102](#1102)) ([9cdab00](9cdab00)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: cattle-ops-releaser-2[bot] <134548870+cattle-ops-releaser-2[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
Some organizations may disallow configuring block public access settings on individual S3 buckets. For example, the organization may use account level configuration to block public access on all buckets.
To support this, we add the field
create_aws_s3_bucket_public_access_block
to therunner_worker_cache
variable.We add
count
to theaws_s3_bucket_public_access_block
resource to control its creation and use themoved
keyword to ensure that existing instances of this resource are not recreated due to this change.Migrations required
No. Migrations are automatically handled by
moved
keyword.Verification
Applied this module with the
create_aws_s3_bucket_public_access_block
field set tofalse
. Theaws_s3_bucket_public_access_block
resource was not created. All other resources were created as expected.