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
When creating an index using opensearch_index resource with dynamic parameter set to falsethe Terraform resource goes into an inconsistency loop. The value in the mapping provided to the TF resource is of type boolean but the value that is stored in Terraform state is of type string. This causes Terraform to apply the change every time it is executed regardless if the configuration changed.
I think the root cause for this inconsistency is that the OpenSearch returns the parameter value as a string when sending a request to GET testindex1/_mapping endpoint.
How can one reproduce the bug?
Provision a new OpenSearch cluster
Create a new index using the opensearch_index resource in the cluster and set the dynamic parameter to false
Replan the project without any changes
Terraform should ask to recreate the index because of type mismatch
What is the expected behavior?
The expected outcome is that when a mapping for dynamic field is applied the state no longer has the inconsistency and after initial apply it will not have changes unless the specified mapping changes.
What is your host/environment?
Opensearch Provider version 2.3.1
OpenSearch 2.17
The text was updated successfully, but these errors were encountered:
What is the bug?
When creating an index using
opensearch_index
resource with dynamic parameter set tofalse
the Terraform resource goes into an inconsistency loop. The value in the mapping provided to the TF resource is of type boolean but the value that is stored in Terraform state is of type string. This causes Terraform to apply the change every time it is executed regardless if the configuration changed.I think the root cause for this inconsistency is that the OpenSearch returns the parameter value as a string when sending a request to
GET testindex1/_mapping
endpoint.How can one reproduce the bug?
opensearch_index
resource in the cluster and set the dynamic parameter tofalse
What is the expected behavior?
The expected outcome is that when a mapping for dynamic field is applied the state no longer has the inconsistency and after initial apply it will not have changes unless the specified mapping changes.
What is your host/environment?
Opensearch Provider version 2.3.1
OpenSearch 2.17
The text was updated successfully, but these errors were encountered: