-
Notifications
You must be signed in to change notification settings - Fork 116
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
Stop using initialApiVersion annotation #837
Conversation
In the 1.2.0 release, we added the pulumi.com/initialApiVersion annotation, which was used internally by the provider. This caused the side effect of requiring updates to all existing resources. This change instead stores that information in the state file, and no longer creates an annotation. To avoid further disruption, the annotation is not removed if it already exists, but will be ignored by the provider.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand how Update
works if there isn't already an annotation. It seems like we're expect it will be in the state bag or the annotations, but some resources will have neither of these—right?
f646cfc
to
a38489e
Compare
@hausdorff You're right; I was not handling pre-1.2 resources correctly. Fixed in the latest commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, I think this works.
Proposed changes
In the 1.2.0 release, we added the pulumi.com/initialApiVersion annotation,
which was used internally by the provider. This caused the side effect of
requiring updates to all existing resources.
This change instead stores that information in the state file, and no longer
creates an annotation. To avoid further disruption, the annotation is not
removed if it already exists, but will be ignored by the provider.
Related issues (optional)
Fixes #834