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
I wasn’t sure whether this should be a bug report, as in hindsight, it might be expected behavior. However, I wanted to share it for visibility.
After upgrading to Terraform provider version 1.19.2, we noticed that order search was unexpectedly disabled in our Commercetools setup. Upon investigating, we found that the enable_search_index_orders setting now defaults to true only when explicitly defined. Since we hadn’t specified this setting in our configuration, the default behavior changed, causing order searches to stop working.
That said, this may not technically be a bug, as our Terraform plan did indicate the change—we just overlooked it. My assumption is that this behavior is related to this change, but I’m not very proficient in Go, so I can’t say for certain.
Anyway, thanks for the good work 👍
Cheers,
Robin
The text was updated successfully, but these errors were encountered:
Hi @robin-hps yeah this was an additional feature that had some impact on pre-existing environments. We tried improving the handling of these values by explicitly setting defaults to the same as the commercetools api, but I guess in pre-existing deployments that had different values where this was not specified in the config it would reset them to defaults under the hood.
I wasn’t sure whether this should be a bug report, as in hindsight, it might be expected behavior. However, I wanted to share it for visibility.
After upgrading to Terraform provider version 1.19.2, we noticed that order search was unexpectedly disabled in our Commercetools setup. Upon investigating, we found that the enable_search_index_orders setting now defaults to true only when explicitly defined. Since we hadn’t specified this setting in our configuration, the default behavior changed, causing order searches to stop working.
That said, this may not technically be a bug, as our Terraform plan did indicate the change—we just overlooked it. My assumption is that this behavior is related to this change, but I’m not very proficient in Go, so I can’t say for certain.
Anyway, thanks for the good work 👍
Cheers,
Robin
The text was updated successfully, but these errors were encountered: