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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add data resource to lookup privatelink information. #514

Closed
jhunter1-onetrust opened this issue Jul 8, 2022 · 0 comments · Fixed by #533
Closed

Add data resource to lookup privatelink information. #514

jhunter1-onetrust opened this issue Jul 8, 2022 · 0 comments · Fixed by #533
Assignees
Milestone

Comments

@jhunter1-onetrust
Copy link

Description

The Elastic documentation provides a list of Azure Private Link Service Aliases that are used when creating a private link and its necessary resources. In order to simplify the deployment some, we're having to keep a map of these items in a locals.tf file in order to quickly, and easily, pull back the correct information.

Unfortunately this requires us to have to regularly check for updates to this list and update our file accordingly.

As an alternative, can we get a data lookup for this information where we simply provide the region and the alias and the zone domain name are returned as consumable attributes?

Your Environment

We created two modules for simplified deployments. One is our Elastic private link module that sets up the private link connection, hosted zone, etc. and where the locals.tf map is found. The second module is one specifically for deployments that consumes outputs from the private link module in order to automatically configure traffic filters, proper region, etc.

We have multiple vnets across multiple regions. One private link setup per vnet, with one-to-many Elastic deployments associated to each vnet.

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

Successfully merging a pull request may close this issue.

4 participants