Add a description of policyfile design and status #122
Conversation
|
👍 Neat write up. Might be a good idea to share this in the ML and maybe use of of next weeks Chef Office Hours to get questions / talk about this stuff. |
|
I have to say this is the first RFC i'm actually excited to see. |
| policyfile, and run the recipes specified by the policyfile's run list. | ||
| A given revision of a policyfile can be promoted through deployment | ||
| stages to safely and reliably deploy new configuration to your | ||
| infrastructure. |
There was a problem hiding this comment.
Maybe would be nice to specify where to save the Policifyle: what is its place from the FS/repo point of view. Or at least list some examples. AFAIK, Policyfile can be saved within a non-chef application, within a cookbook (similar to Berksfile) or even in your chef-repo/policies (or similar).
There was a problem hiding this comment.
Yeah, you can put it wherever you want, depending on your workflow, but those are the 3 examples we have in mind.
|
@danielsdeleo, nice doc. This new feature sounds very interesting 😃 Excuse me for the flood of questions. |
| upstream ID of the cookbook (such as git revision); for cookbooks loaded | ||
| from local disk, the Policyfile implementation detects if they are in a | ||
| git repo and collects the upstream URL, current revision ID, whether the | ||
| repo is dirty, and whether the commits are pushed to the remote. |
There was a problem hiding this comment.
Why does it need to read the details of the git repo when working with local disk cookbooks? For what purpose? What happens if you are using a non-git SCM? and if you have multiple remotes? I see no need for this.
There was a problem hiding this comment.
As the first paragraph of the section says, the primary purpose is to provide information that might be useful when looking at multiple cookbook revisions with the same name and version number and trying to make sense of them. Additionally, it gives you a head start when debugging issues, especially if you use a workflow that involves uploading cookbooks from path sources on a regular basis.
|
@zuazo I added some sections based on your questions. |
|
OK, thanks @danielsdeleo. No more questions. I'll take a look at the code when I have a free moment. |
I've added a readme for the Policyfile feature so we can point people with questions there for additional info. It describes the overall plan and has a list of not-yet-implemented stuff. The idea is we'll update this as we go.
Thoughts? @opscode/client-engineers