You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
CosmosDB Accounts can have a capability called 'EnableTtlOnCustomPath'.
This capability does not seem to be supported in terraform yet, which means we cannot add it to any cosmosdb account.
The biggest issue is that we have instances created using terraform that now have this capability added, and any terraform plan shows recreation of the cosmosdb account.
I've made this PR with the capability added: #21983
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.
Is there an existing issue for this?
Community Note
Description
CosmosDB Accounts can have a capability called 'EnableTtlOnCustomPath'.
This capability does not seem to be supported in terraform yet, which means we cannot add it to any cosmosdb account.
The biggest issue is that we have instances created using terraform that now have this capability added, and any terraform plan shows recreation of the cosmosdb account.
I've made this PR with the capability added:
#21983
New or Affected Resource(s)/Data Source(s)
azurerm_cosmosdb_account
Potential Terraform Configuration
References
No response
The text was updated successfully, but these errors were encountered: