lp:~harlowja/cloud-init/better-chef-module

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~cloud-init-dev/cloud-init/trunk at revision 1036

cloud-init Commiters: Pending requested 2014-10-11

Diff: 562 lines (+414/-67)

4 files modified

cloudinit/config/cc_chef.py (+247/-58)
cloudinit/util.py (+4/-0)
templates/chef_client.rb.tmpl (+42/-9)
tests/unittests/test_handler/test_handler_chef.py (+121/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1046. By Joshua Harlow on 2014-11-22

Update chef module docstring to reflect the new style

1045. By Joshua Harlow on 2014-10-15

Prefer immutable structures

1044. By Joshua Harlow on 2014-10-14

Use the key contants in the default key => value set

1043. By Joshua Harlow on 2014-10-14

Add a post-run method that can be used to delete validation.pem files

For those who run chef in non-daemon mode, they would like to delete
the validation.pem file if chef finishes as expected to remove that file
from existing in an easy to read manner.

1042. By Joshua Harlow on 2014-10-12

Retain the old behavior for mandatory keys

The keys 'server_url' and 'validation_name' were
previously mandatory, we should retain that behavior
for now.

1041. By Joshua Harlow on 2014-10-12

Add a comment explaining the param path logic

1040. By Joshua Harlow on 2014-10-12

Allow running even if installed

Standardize on using the chef_cfg key 'exec' which can be used
when installing to tell the caller to run the chef client or can
also be used if the client is already installed and its requested
to be ran.

To retain existing behavior 'exec' does not by default assume to
be true, unless explicitly provided or a gems mode install is
requested.

1039. By Joshua Harlow on 2014-10-12

Follow the same constant variable naming scheme for the path tpl keys

1038. By Joshua Harlow on 2014-10-12

Have the caller find the param paths instead of the param creator

1037. By Joshua Harlow on 2014-10-12

Ensure that any template paths have associated directories

When the template provides a path, make sure that before the
template is written that the path that is now in the template
has the associated directory created (if not already created).