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
When the feature to upgrade an existing Cosmos DB mongo version to 3.6 was rolled out to our Cosmos DB, the AllowSelfServeUpgradeToMongo36 was added to a terraform state and caused a force resource replacement.
After upgrading Cosmos DB on the portal, the AllowSelfServeUpgradeToMongo36 feature remains in a terraform state.
I added the AllowSelfServeUpgradeToMongo36 to the tf file, but the Azure provider refused it.
Error: expected capabilities.0.name to be one of [EnableAggregationPipeline EnableCassandra EnableGremlin EnableTable EnableMongo MongoDBv3.4 mongoEnableDocLevelTTL DisableRateLimitingResponses], got AllowSelfServeUpgradeToMongo36
on main.tf line 224, in resource "azurerm_cosmosdb_account" "xxx":
224: resource "azurerm_cosmosdb_account" "xxx" {
I'd like to add support for AlowServeUpgradeToMongo36 to cosmosdb_account.
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!
ghost
locked as resolved and limited conversation to collaborators
Oct 4, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
When the feature to upgrade an existing Cosmos DB mongo version to 3.6 was rolled out to our Cosmos DB, the
AllowSelfServeUpgradeToMongo36
was added to a terraform state and caused a force resource replacement.After upgrading Cosmos DB on the portal, the
AllowSelfServeUpgradeToMongo36
feature remains in a terraform state.https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/39654955-upgrading-existing-accounts-from-mongodb-server-ve
I added the
AllowSelfServeUpgradeToMongo36
to the tf file, but the Azure provider refused it.I'd like to add support for
AlowServeUpgradeToMongo36
to cosmosdb_account.New or Affected Resource(s)
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: