-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Cosmosdb indexing policy capitalization #16086
Comments
Hi @noiano, sorry that your having this issue As part of the 3.0 upgrade we are starting to move towards using the casing specified by the rest API specs and SDK. The provider should be validing the config is using that casing and transparently translating the API responses to casing used in the SDK. It looks like the SDK is using What casing are you using in your config? and what happens when you use |
Hello,
Solved the "problem" ... now terraform doesn't try capitalize the indexing policy any more. Are there any more of these changes? If so where can I find them? Thank you for your time :) |
@noiano thank you for opening this issue. I submitted a PR to fix this issue, setting case-sensitive for |
@noiano For the above context, are you okey if we close this issue? |
Absolutely, thank you for checking in |
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. |
After upgrading to version
v3.0.2
due to the fix of #16068 I noticed a strage behaviour, this time affecting cosmodb resources. Even after a successful apply, just by runningterraform
apply again, I see terraform trying to capitalize theindexing_policy
over and over again.I mean it's no biggie given that it doesn't seem to do much ... It's just an annoyance 😄
Terraform (and AzureRM Provider) Version
Affected Resource(s)
azurerm_cosmosdb_sql_container
Steps to Reproduce
terraform apply
orterraform plan
Community Note
The text was updated successfully, but these errors were encountered: