Add feature to store machine data in node attribute rather than file. #31
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
christinedraper
force-pushed
the
nomachinefile
branch
from
2ccebb8 to
3fa00e0
Compare
|
Added a fix for #25 |
To use this option, specify a driver url of 'ssh:chef' In support of above: 1. Some refactoring of driver.rb. 2. Fixes some warnings with gemspec. 3. Fixes tests for changed location of vagrant insecure key in vagrant 1.7+. 4. Updated readme for above and some out of date info. Also fixes chef-boneyard#29 by using stored transport options if none specified, and fixes chef-boneyard#25 so validation logic accepts windows :port
christinedraper
force-pushed
the
nomachinefile
branch
from
3fa00e0 to
c906199
Compare
|
Thanks @christinedraper ! |
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.
To use this feature, specify a driver url of 'ssh:chef'. This makes it easier to use ssh provisioning from multiple locations. One example use case is using provisioning actions in different phases of Chef Delivery.
In support of above:
Also fixes #29, removing need to specify machine_options in subsequent recipes referring to the same machines (e.g. to destroy them).