-
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
[New Data Source]: aws_cloudfront_origin_access_control #34489
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Being able to fetch a if you look at an example where a single S3 bucket is used by multiple Cloudfront distributions (using different origin paths), all those distro's could reuse the same OAC, instead of having to create separate ones all the time. bucket:
cloudfronts:
performing a new release is then just a path change on the cloudfront. |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.59.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. |
Description
Noticed when I was working on docs in #34416 that there wasn't a data source for
aws_cloudfront_origin_access_control
. Not as useful as the Origin Access Identity since the new version doesn't require building an arn and attaching that to the S3 policy, but could still be used as a template or something along those lines.There's no v2 Cloudfront service yet so could be an easy first feature? Did the PR in v1 but can change it if needed.
Requested Resource(s) and/or Data Source(s)
aws_cloudfront_origin_access_control
Potential Terraform Configuration
References
No response
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: