Closed kaminchu closed 6 months ago
Voting for Prioritization
Volunteering to Work on This Issue
[!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.43.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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Terraform Core Version
1.7.3
AWS Provider Version
5.37.0
Affected Resource(s)
aws_cloudfront_function
Expected Behavior
When updating the code of an aws_cloudfront_function that already has an associated KeyValueStore configured, and subsequently executing terraform apply, the associated KeyValueStore should remain unchanged.
Actual Behavior
Currently, the aws_cloudfront_function does not support the configuration of an associated KeyValueStore, resulting in the deletion of any existing associated KeyValueStores.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Run terraform apply. Then replace contents of the code and run terraform apply again.
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None