Skip to content

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

Merged
merged 2 commits into from
Jul 25, 2018

Conversation

cmeury
Copy link
Contributor

@cmeury cmeury commented Jun 26, 2018

An attempt at resolving #54, maybe someone can pick it up and build on it?

@mumoshu
Copy link
Collaborator

mumoshu commented Jun 27, 2018

@cmeury Thanks for your contribution across projects 👍This LGTM overall, would you mind rebasing?

Also, I'm fine with adding os.Exit(2) on no error but diff(s) in this PR if it's possible. helm diff would return 1 anyway due to the helm restriction, but I guess that we can avoid that by running helm-diff directly.

@mumoshu
Copy link
Collaborator

mumoshu commented Jul 12, 2018

Update:

helm diff would return 1 anyway due to the helm restriction, but I guess that we can avoid that by running helm-diff directly.

This turned out to be not that easy(obviously? 😃) due to that helm-diff needs TILLER_HOST to be set to the tunneled tiller endpoint, which requires us to run helm-diff via the helm plugin system.

@mumoshu
Copy link
Collaborator

mumoshu commented Jul 20, 2018

Trying to rebase this onto master.

Copy link
Collaborator

@mumoshu mumoshu left a 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 :)

@mumoshu mumoshu merged commit 01eba5c into databus23:master Jul 25, 2018
mumoshu added a commit to mumoshu/helm-diff that referenced this pull request Jul 25, 2018
I have mistakenly introduced a build error due to my merge mistake while resolving conflicts in databus23#65. This fixes that.
mumoshu added a commit that referenced this pull request Jul 25, 2018
I have mistakenly introduced a build error due to my merge mistake while resolving conflicts in #65. This fixes that.
mumoshu added a commit to mumoshu/helm-diff that referenced this pull request Jul 25, 2018
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.
mumoshu added a commit to mumoshu/helm-diff that referenced this pull request Jul 25, 2018
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.
mumoshu added a commit to mumoshu/helm-diff that referenced this pull request Jul 25, 2018
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.
mumoshu added a commit that referenced this pull request Jul 25, 2018
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.
@cmeury cmeury deleted the detailed-exitcode branch August 25, 2018 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants