-
Notifications
You must be signed in to change notification settings - Fork 4
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
Support diff --detailed-exitcode #31
Comments
You're very fast with this :) |
@bonddim PR is welcome. |
@bonddim would you have time to take a look at this isuee? thanks so much. |
@yxxhero, |
From my point of view, the issue this fixed and
can be handled as separate issue. The PR only ignore exit code 2, exit code 1 and 3 or higher are still raised as error. Look at hashicorp/setup-terraform#125, they implement the same behavior. I people assume that exit code 2 would not overlap which real errors, otherwise using exit code 2 for detect changes can not be considered as safe. |
@bonddim got it. closed. |
The running
helmfile diff --detailed-exitcode
expect exit code 2 on a success run.From github actions point of view, it's not possible to allow specific exit code. If helm diff detect changes, it would exit with exit code 2 and helmfile, too. This would result into an action failure.
Proposed solution:
Catch the exit code 2 from helmfile and return exit code 0 to GitHub actions. The exit code should be stored into an output variable.
Use-Case: Run the deploy step only if there is a diff.
The text was updated successfully, but these errors were encountered: