-
-
Notifications
You must be signed in to change notification settings - Fork 244
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
Question: How can a wrapper cookbook specify additional systemd options #314
Comments
Unfortunately I am not sure this is something that can currently be set right now using a node attribute. I'm going to have to think a little more about it, but you should be able to use the poise_service_options resource in a wrapper cookbook. The block below should do what you're looking for the systemd provider: poise_service_options node['consul']['service_name'] do
options :systemd, template: 'consul-wrapper:mytemplate.erb'
end |
thanks I'll try that |
This is probably something that we could expose using inversion options (similar to what we do with the download URL). This allows us to override in a policy or wrapper cookbook. You can see an example in our Redis cookbook README. Unfortunately the inversion attribute name is the name of the resource which in this cookbook's case is the service name (consul) and tends to make the node attributes confusing. |
Unfortunately, adding the code you suggested does not change anything. |
I've succeeded by monkey patching your provider in my wrapper cookbook
but I've submitted a cleaner patch in #316 to make this available to everybody |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
On some setups, the LimitNOFILE option is required in the consul service definition.
Is it possible to add this option using the wrapper cookbook pattern?
So far, I've tried to specify attributes such as
default['consul']['service']['options']['template'] = 'consul-wrapper:mytemplate.erb'
(and similar variation) without any luck.
The text was updated successfully, but these errors were encountered: