"trust": {
"accounts": [
{
"trust_all": true,
"account_id": "554443047",
"name": "" # This was removed
}
],
"external": [],
"direct": [] # This was also removed
},
Terraform definition
terraform {
required_version = ">= 0.12.29"
required_providers {
ec = {
source = "elastic/ec"
version = "0.10.0"
}
}
}
provider "ec" {
# ECE installation endpoint
endpoint = "https://public-api.qa.cld.elstc.co"
# If the ECE installation has a self-signed certificate
# setting "insecure" to true is required.
#insecure = false
# APIKey is the recommended authentication mechanism. When
# Targeting the Elasticsearch Service, APIKeys are the only
# valid authentication mechanism.
apikey = "..."
}
data "ec_stack" "latest" {
version_regex = "latest"
region = "aws-eu-west-1"
}
# Create an Elastic Cloud deployment
resource "ec_deployment" "example_minimal" {
# Optional name.
name = "my_example_deployment"
# Mandatory fields
region = "aws-eu-west-1"
version = "8.14.3" #data.ec_stack.latest.version
deployment_template_id = "aws-io-optimized-v2"
# Use the deployment template defaults
elasticsearch = {
hot = {
autoscaling = {}
}
ml = {
autoscaling = {
autoscale = true
}
}
}
kibana = {
topology = {}
}
}
Steps to Reproduce
Create a cluster via TF
Add direct trust settings via adminconsole
Change cluster name via Terraform
Use advanced edit to view Elasticsearch cluster settings and verify cluster trust has been changed (direct trusts removed, and account trust names removed)
With 0.12.0 the provider will not update trust settings unless they have changed. However the reported problems when updating trust settings have not yet been fixed.
Readiness Checklist
Expected Behavior
Trust settings should not be altered unless specified in the terraform file.
Current Behavior
Elasticsearch trust settings are changed by the provider in the following unexpected ways:
An example of Elasticsearch cluster data before TF update:
And after TF Update
Terraform definition
Steps to Reproduce