tripleo-heat-templates/deployment/securetty/securetty-baremetal-ansible.yaml
ramishra b253d564f7 Use server side env merging for ServiceNetMap/VipSubnetMap
This simplifies the ServiceNetMap/VipSubnetMap interfaces
to use parameter merge strategy and removes the *Defaults
interfaces.

Change-Id: Ic73628a596e9051b5c02435b712643f9ef7425e3
2021-05-19 10:16:58 +05:30

48 lines
1.2 KiB
YAML

heat_template_version: wallaby
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. Use
parameter_merge_strategies to merge it with the defaults.
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
host_prep_tasks:
- name: Run securetty role
include_role:
name: tripleo_securetty
vars:
tripleo_ttys: {get_param: TtyValues}