Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

Sign up for GitHub

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

Jump to bottom

add feature to configure expected return/exit codes #55025

Closed
colttt opened this issue Oct 16, 2019 · 3 comments
Closed

add feature to configure expected return/exit codes #55025

colttt opened this issue Oct 16, 2019 · 3 comments
Labels
Confirmed Salt engineer has confirmed bug/feature - often including a MCVE Feature new functionality including changes to functionality and code refactors, etc. Windows
Milestone
Approved

Comments

@colttt
Copy link

colttt commented Oct 16, 2019

It would be very nice if you add a parameter to handle exitcodes, specially in win_pkg. Because some windows software is strange with exit-codes like nextcloud, see nextcloud/desktop#922
@garethgreenaway garethgreenaway added this to the Approved milestone Oct 16, 2019
@garethgreenaway garethgreenaway added Feature new functionality including changes to functionality and code refactors, etc. team-windows Windows labels Oct 16, 2019
@garethgreenaway
Copy link
Contributor

Seems like this would be good to have. @xeacott @twangboy FYI.

@stale
Copy link

stale bot commented Jan 7, 2020

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.

@stale stale bot added the stale label Jan 7, 2020
@sagetherage sagetherage added the Confirmed Salt engineer has confirmed bug/feature - often including a MCVE label Jan 9, 2020
@stale
Copy link

stale bot commented Jan 9, 2020

Thank you for updating this issue. It is no longer marked as stale.

@stale stale bot removed the stale label Jan 9, 2020
@saltstack saltstack locked and limited conversation to collaborators Feb 5, 2025
@dwoz dwoz converted this issue into discussion #67654 Feb 5, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
Confirmed Salt engineer has confirmed bug/feature - often including a MCVE Feature new functionality including changes to functionality and code refactors, etc. Windows
Projects
None yet
Milestone
Approved
Development

No branches or pull requests
4 participants
@garethgreenaway @colttt @xeacott @sagetherage