-
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
r/aws_cloudfront_function Always store DEVELOPMENT stage etag in state #19697
Conversation
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.
Welcome @fularac 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTING guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
Any idea when this will be merged/released? |
This was labeled as an enhancement, when this should be considered a bug. This is due to manual modification of cloudfront functions resulting in the provider not being able to modify the cloudfront function. @breathingdust |
Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding. Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author. For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000. For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide. |
…r-aws into b-cloudfront-function-etag
Got access to a sandbox account now acceptance testing is 💯
|
r/aws_cloudfront_function: Add 'live_stage_etag' with the LIVE stage value.
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.
LGTM 🚀.
% make testacc PKG_NAME=internal/service/cloudfront TESTARGS='-run=TestAccCloudFrontFunction_\|TestAccCloudFrontFunctionDataSource_'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/cloudfront/... -v -count 1 -parallel 20 -run=TestAccCloudFrontFunction_\|TestAccCloudFrontFunctionDataSource_ -timeout 180m
=== RUN TestAccCloudFrontFunctionDataSource_basic
=== PAUSE TestAccCloudFrontFunctionDataSource_basic
=== RUN TestAccCloudFrontFunction_basic
=== PAUSE TestAccCloudFrontFunction_basic
=== RUN TestAccCloudFrontFunction_disappears
=== PAUSE TestAccCloudFrontFunction_disappears
=== RUN TestAccCloudFrontFunction_publish
=== PAUSE TestAccCloudFrontFunction_publish
=== RUN TestAccCloudFrontFunction_associated
=== PAUSE TestAccCloudFrontFunction_associated
=== RUN TestAccCloudFrontFunction_Update_code
=== PAUSE TestAccCloudFrontFunction_Update_code
=== RUN TestAccCloudFrontFunction_UpdateCodeAndPublish
=== PAUSE TestAccCloudFrontFunction_UpdateCodeAndPublish
=== RUN TestAccCloudFrontFunction_Update_comment
=== PAUSE TestAccCloudFrontFunction_Update_comment
=== CONT TestAccCloudFrontFunctionDataSource_basic
=== CONT TestAccCloudFrontFunction_Update_code
=== CONT TestAccCloudFrontFunction_disappears
=== CONT TestAccCloudFrontFunction_Update_comment
=== CONT TestAccCloudFrontFunction_publish
=== CONT TestAccCloudFrontFunction_associated
=== CONT TestAccCloudFrontFunction_basic
=== CONT TestAccCloudFrontFunction_UpdateCodeAndPublish
--- PASS: TestAccCloudFrontFunction_disappears (19.92s)
--- PASS: TestAccCloudFrontFunctionDataSource_basic (20.94s)
--- PASS: TestAccCloudFrontFunction_basic (22.93s)
--- PASS: TestAccCloudFrontFunction_publish (31.52s)
--- PASS: TestAccCloudFrontFunction_UpdateCodeAndPublish (31.78s)
--- PASS: TestAccCloudFrontFunction_Update_comment (34.11s)
--- PASS: TestAccCloudFrontFunction_Update_code (34.15s)
--- PASS: TestAccCloudFrontFunction_associated (362.14s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/cloudfront 365.269s
This functionality has been released in v3.65.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 pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #19529
Output from acceptance testing:
I'm unable to complete the acceptance test in our AWS account due to mixture of IAM/auto-compliance issues.