Skip to content
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

[feature] way to know if plan is going to cause any changes from the cli #1495

Closed
camerondavison opened this issue Aug 1, 2016 · 1 comment · Fixed by #1502
Closed

[feature] way to know if plan is going to cause any changes from the cli #1495

camerondavison opened this issue Aug 1, 2016 · 1 comment · Fixed by #1502

Comments

@camerondavison
Copy link
Contributor

currently when a plan is run for a job, it is very pretty for humans to look at but somewhat hard to figure out if anything is going to change from the command through the cli.

One simple fix for this would be to have the return code be either

  • 0 nothing is going to happen
  • 1 something is going to change
  • 130 or something else (error contacting nomad)
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants