This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 170
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
Also, now that ChefDK depends directly on Chef Provisioning, maybe we should remove Chef Provisioning from the omnibus package and just manage the version via ChefDK's gemspec? |
❤️ |
Now that we have both POLICYFILE_README and PROVISION_README, I think we should just create a README or DOCS folder and move these into that |
machine_options(options) | ||
|
||
# This forces a chef run every time, which is sensible for some | ||
# `chef provision` # use cases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unnecessary second #
@tyler-ball I'm cool with that, on the other hand both of these are supposed to be temporary until we have real docs on docs.chef.io. |
danielsdeleo
force-pushed
the
provision-command
branch
from
May 7, 2015 18:29
891ad4c
to
00d868b
Compare
🍰 |
This will be the home of `chef provision` docs until we are confident in the feature's stability.
danielsdeleo
force-pushed
the
provision-command
branch
from
May 8, 2015 01:23
416fd13
to
e2b91b5
Compare
👍 |
ksubrama
pushed a commit
that referenced
this pull request
Jan 11, 2016
Document access to Chef-only private boxes in Atlas.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Adds a
chef provision
command to ChefDK. I created this because, when I was working on a Policyfile "walkthrough" blog post, I had no good way to provision production-y machines (which I needed to properly demonstrate how cookbook "versioning" works in Policyfiles). I mostly like how Chef Provisioning works but I wanted some command line integration for convenience.For now, I'm considering this an experimental feature. It covers my use cases but I'm only scratching the surface of what you can do with Chef Provisioning, so it's possible that some design decision I made will not produce a good user experience for many cases, therefore I want to explicitly reserve the right to make radically breaking changes for a little while. Once this is shipped I'll solicit feedback and we'll see how it goes. When everything seems stable, I'll take off the warning and add a complementary cookbook generator.
@chef/client-core