-
Notifications
You must be signed in to change notification settings - Fork 156
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
opensearch domain warning "ForceNew: No changes for engine_version" #3389
Comments
Thank you for reporting this issue @ploxiln this is indeed a recent change and likely side-effect of pulumi/pulumi-terraform-bridge#1569 . Our team will have a look as soon as we have a chance. |
That makes sense; thanks for the update! |
I was able to reproduce the issue (thanks for the great repro). It looks like pulumi/pulumi-terraform-bridge#1569 set a different log level then TF uses. Running
We should be able to fix this by reducing the default TF log level in the bridge to ERROR (instead of WARN). |
The warning is triggered by the underlying AWS provider, and can be safely ignored. pulumi/pulumi-terraform-bridge#1684 will resolve the issue after it releases. |
What happened?
For all AWS OpenSearch Domain resources managed by my pulumi projects/stacks, I now get this warning in Diagnostics:
There is no actual diff to apply for the opensearch instance, the EngineVersion in particular had no change. I can just ignore the warning and everything continues to work ok, but it does make the plan output messier, and it even corrupts the plan terminal output even more sometimes. Example below. But before that, some more notes:
pulumi.IgnoreChanges([]string{"engineVersion"})
doesn't helpExample of corrupted preview terminal output (happens occasionally):
Example
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: