CosmosDB MongoDB Capabilities can't be set.

[alex0ptr]

Community Note

• 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

We use Terraform to provide a CosmosDB in the MongoDB variant. Every time we run Terraform it wants to perform the following change:

Terraform will perform the following actions:
  ~ module.svhb_state_service_cosmos.azurerm_cosmosdb_account.db
      capabilities.#:               "1" => "0"
      capabilities.1110180979.name: "MongoDBv3.4" => ""

This resource modification alone takes about a minute to perform and therefore slows down the whole template.

Also we can't define the capabilities ourself because if we try with a capabilities block:

  capabilities {
    name = "MongoDBv3.4"    
  }

because then we get a validation error expected capabilities.0.name to be one of [EnableTable EnableGremlin EnableCassandra], got MongoDBv3.4.

Potential Terraform Configuration

Add the following option to capabilities:

capabilities {
  name="MongoDB3.4"
}

alternatively please don't validate the values.

[katbyte]

Hi @alex0ptr,

I have added it to a branch, however when I attempt to test I get the opposite problem:

testing.go:513: Step 0 error: After applying this step, the plan was not empty:

		DIFF:

		UPDATE: azurerm_cosmosdb_account.test
		  capabilities.#:               "0" => "1"
		  capabilities.1110180979.name: "" => "MongoDBv3.4"

Is this a preview feature/something that needs to be enabled on at subscription level?

[tombuildsstuff]

@katbyte I took a quick look into this earlier in the week (since it's related to #1848) - in the Portal it states this can take up to 30m to apply, so it could be an eventual consistency issue where the feature doesn't get enabled behind the scenes for ~20m (so I guess we'd need to poll for this?)

[alex0ptr]

I get the feeling, that this will be hard to maintain because of the many options that might also change quite often. Can someone test what happens if there is a capability that is not documented? If the request fails it may be better to leave validation to Cosmos API.

[katbyte]

Blocked on Azure/azure-sdk-for-go#2864

[ghost]

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!