-
Notifications
You must be signed in to change notification settings - Fork 3
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
Updating to version >=4.9.0 tries to recreate my certificates #173
Comments
Thank you for reporting the issue! I think I can reproduce the issue with upstream also. The previous Pulumi provider version was based on approximately 3.4.0 of upstream, and the new one is ahead of 4.0.4, but even with these versions TF generates replacement plans. There is also hashicorp/terraform-provider-tls#263 The ideal case for us would be if upstream TF provider implemented state upgrades to seamlessly make these upgrades happen. I'll explore what else we can do in the meanwhile.
|
@Sodki does upgrading to https://github.com/pulumi/pulumi-tls/releases/tag/v4.10.0 fix the problem for you for the moment? We've reverted upstream to last known working version and pushed another v4.x.x tag. |
The root cause of the issue is hashicorp/terraform-provider-tls#284 At the very least we should have marked the Pulumi upgrade as a major version bump to match the upstream version bump. We may still do so in the future, but unfortunately the manual workarounds from 284 currently do not work on the Pulumi version. I'll need to make this works before attempting the upgrade again. |
Thank you @t0yv0, version 4.10.0 fixes the problem. 👏 |
Thank you! And apologies for this disruption. |
What happened?
After upgrading to version 4.9.0 or 4.9.1, the provider tries to recreate my certificates. Version 4.8.0 doesn't have this problem. I've noticed the behaviour with
pulumi_tls.SelfSignedCert
andpulumi_tls.CertRequest
, at least.Expected Behavior
Upgrading the provider should keep my certificates as they are.
Steps to reproduce
I have the following resources using version 4.8.0:
When upgrading to version 4.9.0 or 4.9.1 and running Pulumi again, the provider tries to recreate my certificates:
Details:
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: