Create MongoDB v3.6 with azurerm_cosmosdb_account (#4757)

[aristosvo]

Fixes #4757 for service/cosmosdb

FWIW, in #4757 are also validations mentioned. I'm looking into implementing these, but I'm not sure wheter these should be here in a custom validate function or not. If they should be here, the question is if I should break the existing contract to implement these (with more validations) in the schema:

"capabilities": {
	Type:     schema.TypeSet,
	Optional: true,
	Elem: &schema.Resource{
		Schema: map[string]*schema.Schema{
			"EnableMongo": {
				Type:     schema.TypeBool,
				Optional: true,
				Default:  false,
			},
..

[dany74q]

Awesome ! Any idea when this is going to be merged ?
We can't create cosmos accounts w/ the 3.6 backend without this change.

[aristosvo]

@katbyte can you give us an indication when you have time for a review? It are just a few lines of code.

@dany74q I’m using it already myself based on my custom build, I can send it to you if you’d like that or follow the instructions in the repository.

[katbyte]

Hi @aristosvo,

Thanks for the PR. This LGTM 🚀

[katbyte]

Could we get a test that sets this value??

[katbyte]

@aristosvo, wrt validations I really like your idea of adding boolean properties to the capabilities block, however that would be a breaking change that should be done for 2.0.

[ghost]

This has been released in version 1.42.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 = "~> 1.42.0"
}
# ... other configuration ...

[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 👉 hashibot-feedback@hashicorp.com. Thanks!