CosmosDB Mongo API Throughput Management

[rgherta]

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

Hello

It would be great if we could manage throughput at database and collection level as it is done now using the APIs and Azure CLI.

New or Affected Resource(s)

• azurerm_cosmosdb_mongo_database
• azurerm_cosmosdb_mongo_collection

Potential Terraform Configuration

resource "azurerm_cosmosdb_mongo_database" "example" {
  name                = "tfex-cosmos-mongo-db"
  resource_group_name = "${data.azurerm_cosmosdb_account.example.resource_group_name}"
  account_name        = "${data.azurerm_cosmosdb_account.example.name}"
  throughput    = 400   ##add this
}

resource "azurerm_cosmosdb_mongo_collection" "example" {
  name                = "tfex-cosmos-mongo-db"
  resource_group_name = "${data.azurerm_cosmosdb_account.example.resource_group_name}"
  account_name        = "${data.azurerm_cosmosdb_account.example.name}"
  database_name       = "${azurerm_cosmosdb_mongo_database.example.name}"
  throughput    = 400   ##add this
  shard_key           = "uniqueKey"

}

References

• https://www.terraform.io/docs/providers/azurerm/r/cosmosdb_mongo_database.html
• https://www.terraform.io/docs/providers/azurerm/r/cosmosdb_mongo_collection.html
• https://docs.microsoft.com/en-us/cli/azure/cosmosdb/database?view=azure-cli-latest#az-cosmosdb-database-create
• https://docs.microsoft.com/en-us/cli/azure/cosmosdb/collection?view=azure-cli-latest#az-cosmosdb-collection-create

[tombuildsstuff]

hi @rgherta

Thanks for opening this issue :)

Taking a look through this appears to be a duplicate of #3623 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of that one; would you mind subscribing to #3623 for updates?

Thanks!

[rgherta]

Hi @tombuildsstuff it's not quite the same provider resource. I am refering to Mongo API of CosmosDB.

The issue mentioned refers to the SQL resource and only for database level, no mention of colleciton level throughput(which is also impossible to provision atm)

Since the entire CosmosDB service uses different providers resources, for tracking purposes I would let this separate, but as long as we have progress on this issue and we keep in mind it's different resources, I have no objection.

[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!