puppet-watcher/releasenotes/notes/rename-api-opts-e954f36e0ee0e49b.yaml
Takashi Kajinami 2a689b750a Refactor management of [api] parameters
Currently when api service is disabled, puppet-watcher doesn't manage
any parameters in the [api] section. However this behavior is not
required since these parameters are just unused, might leave unmanaged
parameters it once configures, and is just redundant.

This change makes the [api] parameters always managed by puppet.

Also, redundant parameter names, prefixed by 'watcher_api_`` are
renamed because it's very clear the parameters in the ``watcher::api``
class is basically for [api] stuff.

Change-Id: I37362094b2d4b13368658ef3e0b0b0b4be415af2
2022-02-10 22:41:37 +09:00

11 lines
397 B
YAML

---
features:
- |
The following parameters of the ``watcher::api`` class have been deprecaed.
- ``watcher_api_port`` (replaced by ``port``)
- ``watcher_api_max_limit`` (replaced by ``max_limit``)
- ``watcher_api_bind_host`` (replaced by ``bind_host``)
- ``watcher_api_workers`` (replaced by ``workers``)
- ``watcher_api_enable_ssl_api`` (replaced by ``enable_ssl_api``)