-
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
azurerm_cosmosdb_sql_container
doesn't call get throughput api when cosmos account is serverless
#9311
azurerm_cosmosdb_sql_container
doesn't call get throughput api when cosmos account is serverless
#9311
Conversation
/cc @mariussm FYI |
d24ee5d
to
c2e34f6
Compare
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.
Thanks again @ilmax - This LGTM 👍
After this fix, I am seeing my sql_container objects created successfully, but on the next run, Terraform will destroy them and re-create them. This happens every time. Are you seeing the same issue @ilmax ? |
Seems the issue stems from having the following defined, that causes my replacement: unique_key {
paths = []
} |
Tested and works like a charm - awesome work @ilmax |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Fixes #8175, this time for real :)
This is based on #8673 & #9187 /cc @yupwei68
Unfortunately I missed this one in 9187. This should now fix comsosdb SQL serverless.