Make chef repo prefer policyfiles

[danielsdeleo]

• Replace roles/ and environments/ directories with a policies/ directory (also add a comment for how to reverse this if using the code in a custom generator).
• Add a .chef-repo.txt file at the root of generated Chef Repos to allow chef-dk to adjust generator behavior for chef repos
• Use given arguments to chef generate policyfile to set the policy name and run list; add a chef_repo source to generated policies when generating a policy in a chef repo.

[danielsdeleo]

I need to figure out what to do about default_source :chef_repo evaluating relative paths as relative to the cwd instead of relative to the policyfile. If you generate a repo, make a policy in it, and then attempt to chef install that policy, you get this error:

chef install policies/hello.rb
Building policy hello
Expanded run list: recipe[example::default]
Caching Cookbooks...
WARN: bin cookbook missing metadata or no name field, skipping
WARN: demo cookbook missing metadata or no name field, skipping
WARN: lib cookbook missing metadata or no name field, skipping
WARN: spec cookbook missing metadata or no name field, skipping
WARN: test-scripts cookbook missing metadata or no name field, skipping
Error: Failed to generate Policyfile.lock
Reason: (Solve::Errors::NoSolutionError) Unable to satisfy the following requirements:

- `example (>= 0.0.0)` required by `user-specified dependency`

[lamont-granquist]

exercise the oh-dotness of chef-dk and just fix it even though it might be breaking?

[danielsdeleo]

Yeah, I think that's for the best

[danielsdeleo]

With the latest commit, the path argument to chef repo is expanded relative to the dir the policyfiles are in, which is consistent with what we do for cookbooks with a path source.

[randomcamel]

Would it make sense to put this in a single let (maybe at the bottom of the file) rather than having it twice?

[randomcamel]

lgtm, though I can't say I have the full context around the Policyfile implementation.