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
It's "multi-model-ness" appears to just mean that it namespaces other databases (e.g. DocumentDb, MongoDb, ...). Perhaps we can take "inspiration" from the AWS mongo resource or another to handle that child resource?
Personally my use-case is totally DocumentDb-specific but Mongo might be a good way to get the ball rolling.
The text was updated successfully, but these errors were encountered:
At this point this new split-out AzureRM Provider is only shipped with the Terraform 0.10-beta1 - so you'd either need to use the Terraform 0.10 beta, or the azurerm_template_deployment resource in Terraform 0.9 in order take advantage of this functionality for the moment.
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 and limited conversation to collaborators
Apr 1, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A pretty wicked "globally distributed, multi-model database". It would be neat to support it.
It's "multi-model-ness" appears to just mean that it namespaces other databases (e.g. DocumentDb, MongoDb, ...). Perhaps we can take "inspiration" from the AWS mongo resource or another to handle that child resource?
Personally my use-case is totally DocumentDb-specific but Mongo might be a good way to get the ball rolling.
The text was updated successfully, but these errors were encountered: