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
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
A data object to read config from a existing Azure communication service could be helpful in scenarios where the ACS is created somewhere not managed by Terraform. This will allow for a simple way to, for example, read the connection string to be put into a keyvault for our other systems to access.
As a workaround we are now using a null_object to read the connection string with a command, and outputting that to a file on our build environment.
New or Affected Resource(s)/Data Source(s)
azurerm_communication_service
Potential Terraform Configuration
data"azurerm_communication_service""example" {
name ="existing"
resource_group_name ="example"
}
output"connection_string" {
value =data.azurerm_communication_service.example.primary_connection_string
}
References
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
Description
A data object to read config from a existing Azure communication service could be helpful in scenarios where the ACS is created somewhere not managed by Terraform. This will allow for a simple way to, for example, read the connection string to be put into a keyvault for our other systems to access.
As a workaround we are now using a null_object to read the connection string with a command, and outputting that to a file on our build environment.
New or Affected Resource(s)/Data Source(s)
azurerm_communication_service
Potential Terraform Configuration
References
No response
The text was updated successfully, but these errors were encountered: