Document chefdk.* settings
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 18
- Forks
- 23
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
UPDATE: See end of thread first. This was originally an issue requesting the following.
Since 'knife cookbook create' is largely (or will be) deprecated, this is my plea for traditional behavior to be restored where one can use commands that take their default values from $HOME/.some_chef_file (a-la 'knife cookbook create' and knife.rb settings).
$HOME/.chef_cli.rb and something like:
cookbook_email = 'me@myorg.com'
cookbook_license = 'our_chosen_license'
cookbook_copyright = 'whatever'
Or... some way to set attributes and sanely reference include_recipe "#{chefdk_stock_code_generator}"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the end of the issue thread, then identify the chefdk.* settings and related Chef CLI behavior that need coverage. Done means the relevant settings, defaults, and usage are documented clearly, including any agreed replacement for the requested configuration approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100