Skip to content
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

Support multi_az_with_standby_enabled #195

Open
lukehsiao opened this issue Oct 10, 2024 · 1 comment · May be fixed by #196
Open

Support multi_az_with_standby_enabled #195

lukehsiao opened this issue Oct 10, 2024 · 1 comment · May be fixed by #196

Comments

@lukehsiao
Copy link

Describe the Feature

I would like to use multi_az_with_standby_enabled for our opensearch cluster.

image

If I turn this on manually in AWS Console, then re-run terraform plan, I see the following.

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.dev_cluster.module.elasticsearch.aws_opensearch_domain.default[0] will be updated in-place
  ~ resource "aws_opensearch_domain" "default" {
        id                 = "arn:aws:es:us-west-2:redacted-elasticsearch"
        tags               = {
            "Environment"  = "dev"
            "Name"         = "elasticsearch"
            "Namespace"    = "ns"
            "VantaNonProd" = "true"
        }
        # (10 unchanged attributes hidden)

      ~ cluster_config {
          - multi_az_with_standby_enabled = true -> null
            # (9 unchanged attributes hidden)

            # (2 unchanged blocks hidden)
        }

        # (11 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Expected Behavior

There is a configuration option exposed that allows me to enable this setting.

Use Case

I want to follow AWS's recommended best practice.

Describe Ideal Solution

There is a configuration option exposed that allows me to enable this setting.

Alternatives Considered

No response

Additional Context

No response

@lukehsiao
Copy link
Author

I likely could provide a PR for this if this is something the cloudposse team would be interested in supporting.

lukehsiao added a commit to lukehsiao-forks/terraform-aws-elasticsearch that referenced this issue Oct 10, 2024
lukehsiao added a commit to lukehsiao-forks/terraform-aws-elasticsearch that referenced this issue Oct 12, 2024
Note that this bumps the minimum `hashicorp/aws` provider version to
5.15.0, where this parameter was introduced [[1]].

[1]: https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md#5150-august-31-2023
Closes: cloudposse#195
lukehsiao added a commit to lukehsiao-forks/terraform-aws-elasticsearch that referenced this issue Oct 12, 2024
Note that this bumps the minimum `hashicorp/aws` provider version to
5.15.0, where this parameter was introduced [[1]].

The README diff was generated with `make init` and `make readme`, and
introduces some minor unrelated changes.

[1]: https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md#5150-august-31-2023
Closes: cloudposse#195
lukehsiao added a commit to lukehsiao-forks/terraform-aws-elasticsearch that referenced this issue Oct 12, 2024
Note that this bumps the minimum `hashicorp/aws` provider version to
5.15.0, where this parameter was introduced [[1]].

The README diff was generated with `make init` and `make readme`, and
introduces some minor unrelated changes.

[1]: https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md#5150-august-31-2023
Closes: cloudposse#195
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant