-
-
Notifications
You must be signed in to change notification settings - Fork 839
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
Add: ACL depends on ownership_controls #176
Closed
bigfantech
wants to merge
14
commits into
cloudposse:master
from
bigfantech:fix/acl-objectownership-conflict
Closed
Add: ACL depends on ownership_controls #176
bigfantech
wants to merge
14
commits into
cloudposse:master
from
bigfantech:fix/acl-objectownership-conflict
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# AWS changed default ObjectOwnership = Bucket Owner Preferred. # To add ACL `aws_s3_bucket_ownership_controls` must be set to `ObjectWriter` (or) `BucketOwnerPreferred` Ref: https://aws.amazon.com/blogs/aws/heads-up-amazon-s3-security-changes-are-coming-in-april-of-2023/
Incorrect secret name. secrets.REPO_ACCESS_TOKEN derived from other CloudPosse repos, example: https://github.com/cloudposse/terraform-aws-rds-cluster/blob/master/.github/workflows/auto-context.yml
Actions fail with error "refusing to allow a Personal Access Token to create or update workflow `.github/workflows/auto-context.yml` without `workflow` scope" Reason: Incorrect secret name. secrets.REPO_ACCESS_TOKEN derived from other CloudPosse repos, secret ref: https://github.com/cloudposse/terraform-aws-rds-cluster/blob/master/.github/workflows/auto-context.yml
Actions fail with error "refusing to allow a Personal Access Token to create or update workflow `.github/workflows/auto-context.yml` without `workflow` scope" Reason: Incorrect secret name. secrets.REPO_ACCESS_TOKEN derived from other CloudPosse repos, secret ref: https://github.com/cloudposse/terraform-aws-rds-cluster/blob/master/.github/workflows/auto-context.yml
Actions fail with error "refusing to allow a Personal Access Token to create or update workflow `.github/workflows/auto-context.yml` without `workflow` scope" Reason: Incorrect secret name. secrets.REPO_ACCESS_TOKEN derived from other CloudPosse repos, secret ref: https://github.com/cloudposse/terraform-aws-rds-cluster/blob/master/.github/workflows/auto-context.yml
Actions fail with error "refusing to allow a Personal Access Token to create or update workflow `.github/workflows/auto-context.yml` without `workflow` scope" Reason: Incorrect secret name. secrets.REPO_ACCESS_TOKEN derived from other CloudPosse repos, secret ref: https://github.com/cloudposse/terraform-aws-rds-cluster/blob/master/.github/workflows/auto-context.yml
Actions fail with error "refusing to allow a Personal Access Token to create or update workflow `.github/workflows/auto-context.yml` without `workflow` scope" Reason: Incorrect secret name. secrets.REPO_ACCESS_TOKEN derived from other CloudPosse repos, secret ref: https://github.com/cloudposse/terraform-aws-rds-cluster/blob/master/.github/workflows/auto-context.yml
Actions fail with error "refusing to allow a Personal Access Token to create or update workflow `.github/workflows/auto-context.yml` without `workflow` scope" Reason: Incorrect secret name. secrets.REPO_ACCESS_TOKEN derived from other CloudPosse repos, secret ref: https://github.com/cloudposse/terraform-aws-rds-cluster/blob/master/.github/workflows/auto-context.yml
This was referenced Apr 27, 2023
Is there a timeline on merging this Pull Request ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
what
why
So to add ACL
aws_s3_bucket_ownership_controls
must be set toObjectWriter
(or)BucketOwnerPreferred
first.In this PR,
aws_s3_bucket_acl
depends_onaws_s3_bucket_ownership_controls
resource block.aws_s3_bucket_ownership_controls default set to
BucketOwnerEnforced
references