OpenSearch: Model dedicated coordinator nodes as regular fields instead of nested block

[pengw0048]

Description

The ability to configure dedicated coordinator nodes has been added in the recent versions. However, it is not optimal to use a nested block for it, because when using Terraform to turn off dedicated coordinator nodes, it requires two steps:

1. Set aws_opensearch_domain.node_options.node_config.enabled to false -> We need to apply this first so the toggle is off in AWS Console.
2. Remove the node_options block -> Otherwise there is drift in the next Terraform plan + node_options { ... {node_config { enabled = false } } }

If we remove the node_options block in the first place, the provider does not disable dedicated coordinator nodes. Also, we already model dedicated master nodes as regular fields, and so this new option set is better if it follows the same convention.

Affected Resource(s) or Data Source(s)

• aws_opensearch_domain

Potential Terraform Configuration

resource "aws_opensearch_domain" "my_domain" {
  ...
  dedicated_coordinator_enabled = true
  dedicated_coordinator_count = 3
  dedicated_coordinator_type = "..."
}

References

No response

Would you like to implement the enhancement?

No

[github-actions]

Community Guidelines

This comment is added to every new Issue to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Issue and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.