Introduce new remote cluster resource

[ckauf]

Overview

Remote Clusters are a fixed list inside the ec_deployment resource. This list always needs to be provided in total, which makes it impossible to dynamically add and remove remote clusters from other places/modules in the Terraform project.

Possible Implementation

Remote Clusters should be added as their own resource type, for example similar to this:

resource "ec_deployment" "local_cluster" {
  name = "local_cluster"

  region                 = "us-east-1"
  version                = data.ec_stack.latest.version
  deployment_template_id = "aws-io-optimized-v2"

  elasticsearch = { }
  kibana = {}
  enterprise_search = {}
  integrations_server = {}
}

resource "ec_deployment" "remote_cluster" {
  name = "remote_cluster"

  region                 = "us-east-1"
  version                = data.ec_stack.latest.version
  deployment_template_id = "aws-io-optimized-v2"

  elasticsearch = { }
  kibana = {}
  enterprise_search = {}
  integrations_server = {}
}

resource "ec_deployment_remote_cluster" "example" {
  local_cluster_id = ec_deployment.local_cluster.id
  deployment_id    = ec_deployment.remote_cluster.id
  alias            = ec_deployment.remote_cluster.name
  ref_id           = ec_deployment.remote_cluster.elasticsearch.0.ref_id
}

Context

This blocks the usage of the Elastic Cloud Terraform provider and requires to change the configuration tool, which should be avoided

Your Environment

• Version used: 0.10.0
• Running against Elastic Cloud SaaS

[rbjhirst]

+1 for this, it would allow us to manage connections for both cloud clusters and on-premises clusters at the same time.