Using a an overridable systemd unit

[pshroads]

Is anyone successfully using a custom systemd script? This is what I have in my wrapper cookbook 'elsaticsearch-cvent' that calls this public elasticsearch cookbook:

elasticsearch_service 'elasticsearch' do
  action :start
  systemd_source 'systemd_unit_cvent.erb'
  systemd_cookbook 'elasticsearch-cvent'
end

Then I have systemd_unit_cvent.erb in the template section of my ''elsaticsearch-cvent' wrapper cookbook.

But the elasticsearch.service file that gets generated doesn't contain my customizations in my systemd_unit_cvent.erb template file.

Any ideas?

Thanks

[bincentvaret]

Working here, but not the same usage.

Our wrapper is called elasticsearch-wrapper

In the role (ruby role)

'elasticsearch' => {
  'service' => {
      'systemd_cookbook' => 'elasticsearch-wrapper'
  }
 }

and our template is named as the default

cookbooks/elasticsearch-wrapper/templates/systemd_unit.erb

[martinb3]

You can also use the systemd override mechanism directly, e.g. in RHEL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sect-Managing_Services_with_systemd-Unit_Files#brid-Managing_Services_with_systemd-Overriding_Unit_Mod