Update poise-archive and poise-service cookbooks

This commit is contained in:
Greg Karékinian
2018-04-17 12:24:17 +02:00
parent 90bb872305
commit ff2f424ddb
16 changed files with 150 additions and 47 deletions

View File

@@ -256,6 +256,8 @@ process creating a PID file in the given path.
* `reload_signal` Override the service reload signal.
* `stop_signal` Override the service stop signal.
* `user` Override the service user.
* `never_start` Never try to start the service.
* `never_stop` Never try to stop the service.
* `never_restart` Never try to restart the service.
* `never_reload` Never try to reload the service.
* `script_path` Override the path to the generated service script.
@@ -294,6 +296,8 @@ default and will throw an error if a reload signal other than SIGHUP is used.
* `reload_signal` Override the service reload signal.
* `stop_signal` Override the service stop signal.
* `user` Override the service user.
* `never_start` Never try to start the service.
* `never_stop` Never try to stop the service.
* `never_restart` Never try to restart the service.
* `never_reload` Never try to reload the service.
@@ -320,6 +324,8 @@ end
* `reload_signal` Override the service reload signal.
* `stop_signal` Override the service stop signal.
* `user` Override the service user.
* `never_start` Never try to start the service.
* `never_stop` Never try to stop the service.
* `never_restart` Never try to restart the service.
* `never_reload` Never try to reload the service.
* `auto_reload` Run `systemctl daemon-reload` after changes to the unit file. *(default: true)*
@@ -343,6 +349,8 @@ as they are enabled.
#### Options
* `never_start` Never try to start the service.
* `never_stop` Never try to stop the service.
* `never_restart` Never try to restart the service.
* `never_reload` Never try to reload the service.
* `pid_file` Path to PID file that the service command will create.
@@ -350,6 +358,32 @@ as they are enabled.
auto-generated hash based on the service name. If these collide, bad things
happen. Don't do that.
### `dummy`
The `dummy` provider supports launching services directly from Chef itself.
This is for testing purposes only and is entirely unsuitable for use in
production. This is mostly useful when used alongside kitchen-docker.
```ruby
poise_service 'myapp' do
provider :dummy
command 'myapp --serve'
end
```
The service information is written to `/var/run`. The PID file is `service_name.pid`,
the command output is `service_name.out`, and the service parameters are in
`service_name.json`.
#### Options
* `never_start` Never try to start the service.
* `never_stop` Never try to stop the service.
* `never_restart` Never try to restart the service.
* `never_reload` Never try to reload the service.
* `restart_delay` Number of seconds to wait between stop and start when
restarting. *(default: 1)*
## ServiceMixin
For the common case of a resource (LWRP or plain Ruby) that roughly maps to