Closed kohbis closed 8 months ago
Voting for Prioritization
Volunteering to Work on This Issue
It would also be beneficial to have the additional resource to support the values in this key-value store. Suggestion - It may take a map(String), map(other supported types by aws key value store) Then based on diff from last state, it adds a new key, or removes a key, or updates the value in a key.
Then on top of that, it would also need to have a key_value_store as an attribute in aws_cloudfront_function resource such that it can be assigned to the function using the arn/ID of this store that is generated.
Any chance this PR can get looked at? Would really like to start using CloudFront Key Value Stores.
This functionality has been released in v5.37.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.
Description
This is the resource creation issue that corresponds to this.
Requested Resource(s) and/or Data Source(s)
Resource(s)
Potential Terraform Configuration
No response
References
Requires https://github.com/hashicorp/terraform-provider-aws/pull/34514.
Would you like to implement a fix?
None