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

Plan exit code map to whether allocations would change + bug fix #1502

Merged
merged 3 commits into from
Aug 3, 2016

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented Aug 2, 2016

This PR makes plan return:

  • 0: No allocations created or destroyed.
  • 1: Allocations created or destroyed.
  • 255: Error determining plan results.

Also fixes an issue in which we improperly classified modifications to KillTimeout as causing a create/destroy update.

Fixes #1495

@dadgar dadgar merged commit 2c48b7b into master Aug 3, 2016
@dadgar dadgar deleted the f-plan-exit-code branch August 3, 2016 18:10
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, 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 Apr 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

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