We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When setting up AWS PrivateLink connection to Coralogix, it is currently needed to source VPC endpoints from Coralogix documentation [1].
A more convenient solution would be to have a datasource which would provide the VPC endpoint URL, similar to how other vendors implement this [2].
Not affecting existing resources.
data "coralogix_system_get_privatelink_config" "coralogix_private_link" {} resource "aws_vpc_endpoint" "coralogix_private_link" { vpc_id = var.vpc_id service_name = data.coralogix_system_get_privatelink_config.coralogix_private_link.aws_vpce_id vpc_endpoint_type = "Interface" ..... }
[1] https://coralogix.com/docs/coralogix-amazon-web-services-aws-privatelink-endpoints/
[2] https://registry.terraform.io/providers/Snowflake-Labs/snowflake/latest/docs/data-sources/system_get_privatelink_config
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
When setting up AWS PrivateLink connection to Coralogix, it is currently needed to source VPC endpoints from Coralogix documentation [1].
A more convenient solution would be to have a datasource which would provide the VPC endpoint URL, similar to how other vendors implement this [2].
New or Affected Resource(s)
Not affecting existing resources.
Potential Terraform Configuration
References
[1] https://coralogix.com/docs/coralogix-amazon-web-services-aws-privatelink-endpoints/
[2] https://registry.terraform.io/providers/Snowflake-Labs/snowflake/latest/docs/data-sources/system_get_privatelink_config
Community Note
👍 reaction to the original
issue to help the community and maintainers prioritize this request
The text was updated successfully, but these errors were encountered: