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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: