Fix Automate v2 deploy guard condition #260
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Graham Davison <[email protected]>
Signed-off-by: Graham Davison <[email protected]>
… of final installation Signed-off-by: Graham Davison <[email protected]>
gdavison
force-pushed
the
fix-automate-guard
branch
from
ff71342 to
35b59fa
Compare
|
The AppVeyor failure is due to #262 |
|
similar changes have already been applied |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The
chef_automatev2resource has a guard condition when executing the deploy command. All other uses ofchef-automatehave the full path, but the invocation in the guard does not.Issues Resolved
Fixes #258
Includes #261
Check List