44ef2a3ec1
The new master branch should point now to rocky. So, HOT templates should specify that they might contain features for rocky release [1] Also, this submission updates the yaml validation to use only latest heat_version alias. There are cases in which we will need to set the version for specific templates i.e. mixed versions, so there is added a variable to assign specific templates to specific heat_version aliases, avoiding the introductions of error by bulk replacing the the old version in new releases. [1]: https://docs.openstack.org/heat/latest/template_guide/hot_spec.html#rocky Change-Id: Ib17526d9cc453516d99d4659ee5fa51a5aa7fb4b
49 lines
1.3 KiB
YAML
49 lines
1.3 KiB
YAML
heat_template_version: rocky
|
|
|
|
description: >
|
|
Configure securetty values
|
|
|
|
parameters:
|
|
ServiceData:
|
|
default: {}
|
|
description: Dictionary packing service data
|
|
type: json
|
|
ServiceNetMap:
|
|
default: {}
|
|
description: Mapping of service_name -> network name. Typically set
|
|
via parameter_defaults in the resource registry. This
|
|
mapping overrides those in ServiceNetMapDefaults.
|
|
type: json
|
|
DefaultPasswords:
|
|
default: {}
|
|
type: json
|
|
RoleName:
|
|
default: ''
|
|
description: Role name on which the service is applied
|
|
type: string
|
|
RoleParameters:
|
|
default: {}
|
|
description: Parameters specific to the role
|
|
type: json
|
|
EndpointMap:
|
|
default: {}
|
|
description: Mapping of service endpoint -> protocol. Typically set
|
|
via parameter_defaults in the resource registry.
|
|
type: json
|
|
TtyValues:
|
|
default: {}
|
|
description: Configures console values in securetty
|
|
type: json
|
|
constraints:
|
|
- length: { min: 1}
|
|
|
|
outputs:
|
|
role_data:
|
|
description: Console data for the securetty
|
|
value:
|
|
service_name: securetty
|
|
config_settings:
|
|
tripleo::profile::base::securetty::tty_list: {get_param: TtyValues}
|
|
step_config: |
|
|
include ::tripleo::profile::base::securetty
|