You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of the latest version of the provider, we can manage the cluster.routing.allocation.awareness attribute, but not the cluster.routing.allocation.awareness.force.zone.values option, which are often combined together.
What solution would you like?
It would be great if the provider could add support for "cluster.routing.allocation.awareness.force.zone.values" so that we don't have to manually add this option to the cluster settings.
What alternatives have you considered?
Manually adding the cluster.routing.allocation.awareness.force.zone.values after terraform has run it's course.
Is your feature request related to a problem?
As of the latest version of the provider, we can manage the cluster.routing.allocation.awareness attribute, but not the cluster.routing.allocation.awareness.force.zone.values option, which are often combined together.
What solution would you like?
It would be great if the provider could add support for "cluster.routing.allocation.awareness.force.zone.values" so that we don't have to manually add this option to the cluster settings.
What alternatives have you considered?
Manually adding the cluster.routing.allocation.awareness.force.zone.values after terraform has run it's course.
Do you have any additional context?
Here are some links to the option in question:
opensearch.org - Forced awareness
elastic.org - Forced awareness
The text was updated successfully, but these errors were encountered: