fa2800419e
This patch migrates all of the remaining non-unique variable names in the security role to a pattern that begins with `security_*`. This will reduce potential variable collisions with other roles. This is a breaking change for deployers and users who are moving from the liberty or stable/mitaka branches to master. Release notes are included with additional details to help with the transition. Closes-Bug: 1578326 Change-Id: Ib716e81e6fed971b21dc5579ae1a871736e21189
21 lines
563 B
YAML
21 lines
563 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
All variables in the security role are now prepended with ``security_`` to
|
|
avoid collisions with variables in other roles. All deployers who have
|
|
used the security role in previous releases will need to prepend all
|
|
security role variables with ``security_``.
|
|
|
|
For example, a deployer could have disabled direct root ssh logins with the
|
|
following variable:
|
|
|
|
.. code-block:: yaml
|
|
|
|
ssh_permit_root_login: yes
|
|
|
|
That variable would become:
|
|
|
|
.. code-block:: yaml
|
|
|
|
security_ssh_permit_root_login: yes
|