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

Cannot configure supermarket's sysctl attributes #56

Open
jayhendren opened this issue Jul 17, 2017 · 0 comments
Open

Cannot configure supermarket's sysctl attributes #56

jayhendren opened this issue Jul 17, 2017 · 0 comments

Comments

@jayhendren
Copy link

jayhendren commented Jul 17, 2017

Cookbook version

3.0.0

Chef-client version

12.17.44

Platform Details

RHEL 7

Scenario:

When writing a recipe that includes both the sysctl and supermarket-omnibus-cookbook default recipes, the embedded chef-solo instance that Supermarket uses to configure itself contends with my recipe for control over the file /etc/sysctl.d/99-chef-attributes.rb.

Supermarket has some configuration parameters that allow the admin to alter the path for the sysctl conf file that it writes (as well as other arbitrary attributes for the sysctl cookbook embedded in Supermarket); however, these parameters are not configurable by supermarket-omnibus-cookbook. This is a request to add attributes (or any other kind of interface) to supermarket-omnibus-cookbook to allow adjusting these sysctl configuration parameters.

For instance, a parameter that I would like to adjust is default['sysctl']['conf_file'] in /etc/supermarket/supermarket.rb (I am not sure what this corresponds to in /etc/supermarket/supermarket.json). I tried setting the node attribute in my recipe default['supermarket_omnibus']['config']['sysctl']['conf_file'], which gets put in to /etc/supermarket/supermarket.json as { "sysctl": { "conf_file": "..." } }, but doesn't seem to have the desired effect.

Steps to Reproduce:

Converge a node that has both sysctl::default and supermarket-omnibus-cookbook::default and sets some custom sysctl values.

Expected Result:

n/a

Actual Result:

n/a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant