-
Notifications
You must be signed in to change notification settings - Fork 292
return non-zero exitcode when encountering any change on upgrade #65
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
Conversation
@cmeury Thanks for your contribution across projects 👍This LGTM overall, would you mind rebasing? Also, I'm fine with adding |
Update:
This turned out to be not that easy(obviously? 😃) due to that helm-diff needs |
Trying to rebase this onto master. |
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.
Thanks for your contribution @cmeury! This should be a great step forward to make helm GitOps friendly :)
I have mistakenly introduced a build error due to my merge mistake while resolving conflicts in databus23#65. This fixes that.
I have mistakenly introduced a build error due to my merge mistake while resolving conflicts in #65. This fixes that.
This feature is enabled only when the `--detailed-exitcode` flag (databus23#65) is provided. Supports `upgrade`, `revision` and `rollback` sub-commands. Resolves databus23#54, but only after helm/helm#4367 as released with helm v2.11.0, probably.
This feature is enabled only when the `--detailed-exitcode` flag (databus23#65) is provided. Supports `upgrade`, `revision` and `rollback` sub-commands. Resolves databus23#54, but only after helm/helm#4367 is released with helm v2.11.0, probably.
This feature is enabled only when the `--detailed-exitcode` flag (databus23#65) is provided. Supports `upgrade`, `revision` and `rollback` sub-commands. Resolves databus23#54, but only after helm/helm#4367 is released with helm v2.11.0, probably.
This feature is enabled only when the `--detailed-exitcode` flag (#65) is provided. Supports `upgrade`, `revision` and `rollback` sub-commands. Resolves #54, but only after helm/helm#4367 is released with helm v2.11.0, probably.
An attempt at resolving #54, maybe someone can pick it up and build on it?