Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for azurerm_communication_services data object #21736

Closed
1 task done
Justnuked opened this issue May 10, 2023 · 0 comments 路 Fixed by #22426
Closed
1 task done

Support for azurerm_communication_services data object #21736

Justnuked opened this issue May 10, 2023 · 0 comments 路 Fixed by #22426

Comments

@Justnuked
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants