Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Configurable Option to Change Default Cookbook Generation policy_mode #43

Open
jschripsema opened this issue Oct 4, 2019 · 1 comment
Labels
Aspect: UX How users feel interacting with the project, focusing on function, ease-of-use and accessibility. Triage: Confirmed Indicates and issue has been confirmed as described. Triage: Feature Request Indicates an issue requesting new functionality. Type: Enhancement Adds new functionality.

Comments

@jschripsema
Copy link

Describe the Enhancement:

I would like to have a local setting that I can set, similar to chefdk.generator.license, that allows me to change the default behavior of the cookbook generator to generate berks cookbooks by default. Maybe something like chefdk.generator.policy_mode false

Describe the Need:

Anyone that regularly generates cookbooks with pipelines or development process that are tied to using Berksfile cookbooks would like a tunable parameter that they can set on their development workstation to default to this cookbook style.

Current Alternative

When generating each cookbook, you can specify -b or --berks flags. This isn't ideal as there is one more step that we could forget or forget to inform someone we're helping learn our cookbook development processes.

Can We Help You Implement This?:

Submitting open source code is, unfortunately, difficult at my current place of employment.

@tyler-ball tyler-ball transferred this issue from chef-boneyard/chef-dk Oct 7, 2019
@tyler-ball tyler-ball added Aspect: UX How users feel interacting with the project, focusing on function, ease-of-use and accessibility. Triage: Confirmed Indicates and issue has been confirmed as described. Triage: Feature Request Indicates an issue requesting new functionality. Type: Enhancement Adds new functionality. labels Oct 7, 2019
@tyler-ball
Copy link
Contributor

Triaged and moved this to chef-cli where chef generate code now lives

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aspect: UX How users feel interacting with the project, focusing on function, ease-of-use and accessibility. Triage: Confirmed Indicates and issue has been confirmed as described. Triage: Feature Request Indicates an issue requesting new functionality. Type: Enhancement Adds new functionality.
Projects
None yet
Development

No branches or pull requests

2 participants