-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
helm: rename status conditional UpdateError to UpgradeError #3269
helm: rename status conditional UpdateError to UpgradeError #3269
Conversation
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.
Why is this change necessary? If it is, it is definitely a breaking change and need a deprecation strategy.
Hi @estroz, The fragment was updated with the info. |
For Helm based-Operator be more aligned with Helm the `UpdateError` was renamed to `UpgradeError`. | ||
Note that it is NOT a breaking change for the Helm based-Operators itself, however, if you have any | ||
script or code implemented which is using this status to perform checks then, will be required replace | ||
`UpdateError` for `UpgradeError` in this places. |
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.
Hi @estroz,
What we are changing here is the status name which will appear in the CR.status to be aligned with helm ( part of the "new" helm-operator ). I agree that users might be checking it due to a script, for example, the status for tests and etc and then, it would be a breaking change for them but not for o Helm based-Operator itself.
My idea/suggestion is we do it before release 1.0.0 image for users is able to move smoothly.
@joelanford wdyt?
The status conditional `UpdateError` was renamed to `UpgradeError` to better align with Helm nomenclature. | ||
This change just affects Helm based-operators. |
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.
The status conditional `UpdateError` was renamed to `UpgradeError` to better align with Helm nomenclature. | |
This change just affects Helm based-operators. | |
In Helm-based operators, the `UpdateError` condition reason was renamed to `UpgradeError` to better align with Helm nomenclature. |
# Migration can be defined to automatically add a section to | ||
# the migration guide. This is required for breaking changes. | ||
migration: | ||
header: `UpdateError` status for Helm based-Operator was ranamed |
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.
header: `UpdateError` status for Helm based-Operator was ranamed | |
header: "Helm: rename condition reason `UpdateError` to `UpgradeError`" |
body: > | ||
For Helm based-Operator be more aligned with Helm the `UpdateError` was renamed to `UpgradeError`. | ||
Note that it is NOT a breaking change for the Helm based-Operators itself, however, if you have any | ||
script or code implemented which is using this status to perform checks then, will be required replace | ||
`UpdateError` for `UpgradeError` in this places. |
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.
Use the yaml |
operator instead of >
for the migration body so we can have separate paragraphs for easier readability. We should probably make this change in the fragment template.
Also some general grammar/syntax suggestions.
body: > | |
For Helm based-Operator be more aligned with Helm the `UpdateError` was renamed to `UpgradeError`. | |
Note that it is NOT a breaking change for the Helm based-Operators itself, however, if you have any | |
script or code implemented which is using this status to perform checks then, will be required replace | |
`UpdateError` for `UpgradeError` in this places. | |
body: | | |
For Helm-based operators to be more aligned with Helm, the `UpdateError` condition | |
reason was renamed to `UpgradeError` for the `ReleaseFailed` condition. | |
Note that this is **NOT** a breaking change for Helm-based operators themselves. | |
However, any script or code that is depending on this condition reason must be updated | |
to use `UpgradeError` instead of `UpdateError`. |
@estroz This was an oversight from the very beginning. Helm has always used "upgrade" to refer to releases, not "update". I think this is a good time to get this in before 1.0. I'm not sure how a deprecation for this would work without us basically duplicating the entire condition and also renaming the condition type from |
@joelanford @camilamacedo86 I think we have to do a hard break. |
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.
/lgtm
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.
/lgtm
Hi, is there a discussion on why we are leaving the reason as Update but not Upgrade? Thanks. |
Hi @mikeshng, Good catcher, we should update the Reason as well. Really tks for the check. It passed. I am doing a pr for that. |
Description of the change:
Motivation for the change: