-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Have an alias to use dryrun=True instead of test=True #45376
Comments
@thatch45 Would you weighing in on this one? |
then it would be 100% safe, the trick would be to pop the key from the kwargs |
@thatch45 Thanks! Adding the Feature label. |
Yes, this is something that would take all of 15 minutes to add and we should have added it long ago |
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. |
up |
Thank you for updating this issue. It is no longer marked as stale. |
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. |
up |
Thank you for updating this issue. It is no longer marked as stale. |
Description of Issue/Question
Some new salt users I came across told me that the test=True could be confusing and would prefer to have a more standard dryrun terminology for what test=True does in salt. I thought I'd start the discussion here about having an alias that does this.
Is it technically difficult to have an alias for dryrun=test which adds test=True early enough to provide such a functionality ?
Doing a grep for dryrun in the code I find that some states already use this argument so if we go down that road we need to make sure they don't break (pkgng, rsync, dockermod)
The text was updated successfully, but these errors were encountered: