-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify the scope of Cosmos DB connection strings in Terraform output #9621
Comments
Taking a look through here it appears the
|
@tombuildsstuff how do you wanna break them up, based on description? Wouldn't that be a bit too flaky? |
@favoretti I don't see another option unfortunately, we'll have to do this conditionally like so:
which should avoid any breaking changes to this on the Azure side, by setting an empty string by default - WDYT? |
Yeah, that's the only way I saw as well, unfortunately, but now I'm kinda wondering how many combinations would there be, since that one has "SQL" in it. Mongo would have its own set, gremlin its own, etc, etc? |
@favoretti sorry missed this ping - agreed it's possible there's multiple combinations available here, but I think we could likely add those as folks need them, others could make sense on the other resources too (e.g. on |
Just came across this. I think that at least |
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. |
Community Note
Description
Scope of Cosmos DB connection strings needs to be specified in Terraform output to reflect the same level of details that Azure CLI provides.
Currently Terraform spits an array of connection strings that looks like below:
Output example when using
az cosmosdb keys list --type connection-strings
New or Affected Resource(s)
References
The text was updated successfully, but these errors were encountered: