You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sudharsh opened this issue
Feb 10, 2015
· 3 comments
Labels
Bugbroken, incorrect, or confusing behaviorCorerelates to code central or existential to SaltP2Priority 2Salt-SSHseverity-low4th level, cosemtic problems, work around existsstale
Been playing around with custom salt modules and grains along with salt-ssh. I found that any errors in the modules or grains aren't bubbled up and are ignored silently. The -l debug is useful but it would be great if the salt-ssh returns an non-zero exit code atleast as a hint that something went wrong.
The text was updated successfully, but these errors were encountered:
@sudharsh Thanks for filing this report! Yes, we need to get a more standardized approach to exit codes and we're working on it. We've got a couple of issues open surrounding this idea, but none are specifically related to salt-ssh.
Can you provide the links to those specific issues. I understand that salt
master minion defines the awesomeness of the stack but Id love to dig in
through the code.
On 10-Feb-2015 10:31 pm, "Nicole Thomas" notifications@github.com wrote:
@sudharshhttps://github.com/sudharsh Thanks for filing this report!
Yes, we need to get a more standardized approach to exit codes and we're
working on it. We've got a couple of issues open surrounding this idea, but
none are specifically related to salt-ssh.
—
Reply to this email directly or view it on GitHub #20545 (comment).
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.
Bugbroken, incorrect, or confusing behaviorCorerelates to code central or existential to SaltP2Priority 2Salt-SSHseverity-low4th level, cosemtic problems, work around existsstale
Been playing around with custom salt modules and grains along with salt-ssh. I found that any errors in the modules or grains aren't bubbled up and are ignored silently. The
-l debug
is useful but it would be great if the salt-ssh returns an non-zero exit code atleast as a hint that something went wrong.The text was updated successfully, but these errors were encountered: