-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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 a aws_s3_access_point_policy
resource to prevent cycle errors
#12235
Comments
Related: |
Note that the new resource will be named Also, until the next major version of the Terraform AWS Provider (v4.0.0), note that the |
This functionality has been released in v3.66.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
This issue was originally opened by @AlexEshoo as hashicorp/terraform#24258. It was migrated here as a result of the provider split. The original body of the issue is below.
Current Terraform Version
Use-cases
When creating an AWS S3 Access Point, a common task is to attach a policy to the access point.
Terraform provides this with the
policy
attribute of theaws_s3_access_point
resource, but it cannot be used with theaws_iam_policy_document
datasource when the document references the ARN of the access point without causing cycle errors.Attempted Solutions
This causes cycle errors due to the circular reference.
Proposal
This problem is resolved for the
aws_s3_bucket
resource by having a separate resource namedaws_s3_bucket_policy
that can be used to link the two resources without circular references. An example is demonstrated hereThe proposal would be to create a similar
aws_s3_access_point_policy
resource that would handle updating the policy on the access point after creation.References
The text was updated successfully, but these errors were encountered: