-
Notifications
You must be signed in to change notification settings - Fork 91
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
Data Source: ec_deployment doesn't expose Fleet (integration server only show APM http endpoint) #875
Comments
@slideroh I had a look and am able to retrieve the fleet endpoint using the following: Is this what you are looking for? full exampleterraform {
required_providers {
ec = {
source = "elastic/ec"
version = "0.12.2"
}
}
}
variable "apikey" {}
provider "ec" {
apikey = var.apikey
}
data "ec_stack" "latest" {
version_regex = "latest"
region = "gcp-us-east1"
}
resource "ec_deployment" "stack" {
name = "hosted_test_deployment"
region = "gcp-us-east1"
version = data.ec_stack.latest.version
deployment_template_id = "gcp-cpu-optimized"
elasticsearch = {
hot = {
autoscaling = {}
}
}
kibana = {}
enterprise_search = {}
integrations_server = {}
}
output "fleet" {
value = ec_deployment.stack.integrations_server.endpoints.fleet
} |
You're using
returns:
As you can see, with http/s endpoint there are only:
|
Aah missed that part (completely read over it) my bad. |
Overview
I'd like to see http/https endpoint of Fleet, as it's visible in a portal. IntegrationServer returns only APM, there is no possibility to get Fleet endpoint, without using
replace
in terraform.Also it would be great idea to expose custom endpoint, which is something like:
replace(replace(data.ec_deployment.dev.kibana[0].https_endpoint, data.ec_deployment.dev.kibana[0].resource_id, data.ec_deployment.dev.alias),":443","")
Possible Implementation
Testing
Context
Your Environment
The text was updated successfully, but these errors were encountered: