new resource "azurerm_spring_cloud_app_cosmosdb_association" #11307
Conversation
ghost
added
|
|
||
| * `cosmosdb_account_id` - (Required) Specifies the ID of the CosmosDB Account. Changing this forces a new resource to be created. | ||
|
|
||
| * `api_type` - (Required) Specifies the api type which should be used when connecting to the CosmosDB Account. Possible values are `cassandra`, `gremlin`, `mongo`, `sql` or `table`. Changing this forces a new resource to be created. |
There was a problem hiding this comment.
couldn't we determine this from the supplied cosmosdb_x property? and then remove this
There was a problem hiding this comment.
@katbyte yes, we could do that. I am just afraid that table type does not need to supply those optional property. It may be not easy for users to understand the difference
There was a problem hiding this comment.
does it make sense to even allow specifying type without the cosmosdb property? and the api doesn't error when they are all left empty?
There was a problem hiding this comment.
for all api type, cosmosDB account is required. For api type table, no more property is needed. For the rest api type, Additional property needs to be provided
There was a problem hiding this comment.
ahh that makes sense - thanks
|
This has been released in version 2.57.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.57.0"
}
# ... other configuration ... |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
cosmosdb supports 5 different sub type association. I combined them in one resource, please check whether it's ok or do I need to split into different sub resource.