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
38 lines
932 B
YAML
38 lines
932 B
YAML
heat_template_version: rocky
|
|
description: 'All Hosts Config'
|
|
|
|
parameters:
|
|
hosts:
|
|
type: string
|
|
|
|
resources:
|
|
|
|
hostsConfigImpl:
|
|
type: OS::Heat::SoftwareConfig
|
|
properties:
|
|
group: script
|
|
inputs:
|
|
- name: hosts
|
|
default:
|
|
list_join:
|
|
- ' '
|
|
- str_split:
|
|
- '\n'
|
|
- {get_param: hosts}
|
|
config: {get_file: scripts/hosts-config.sh}
|
|
|
|
outputs:
|
|
config_id:
|
|
description: The ID of the hostsConfigImpl resource.
|
|
value:
|
|
{get_resource: hostsConfigImpl}
|
|
hosts_entries:
|
|
description: |
|
|
The content that should be appended to your /etc/hosts if you want to get
|
|
hostname-based access to the deployed nodes (useful for testing without
|
|
setting up a DNS).
|
|
value: {get_param: hosts}
|
|
OS::stack_id:
|
|
description: The ID of the hostsConfigImpl resource.
|
|
value: {get_resource: hostsConfigImpl}
|