Carlos Camacho 44ef2a3ec1 Change template names to rocky
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
2018-05-09 08:28:42 +02:00

33 lines
1.1 KiB
YAML

heat_template_version: rocky
description: >
Software Config to install deployment artifacts (tarball's and/or
distribution packages) via HTTP URLs. The contents of the URL's can
be tarballs or distribution packages (RPMs). If a tarball URL is supplied
it is extracted onto the target node during deployment. If a package is
deployed it is installed from the supplied URL. Note, you need the
heat-config-script element built into your images, due to the script group
below.
parameters:
DeployArtifactURLs:
default: []
description: A list of HTTP URLs containing deployment artifacts.
Currently supports tarballs and RPM packages.
type: comma_delimited_list
resources:
DeployArtifacts:
type: OS::Heat::SoftwareConfig
properties:
group: script
inputs:
- name: artifact_urls
default: {list_join: [' ', {get_param: DeployArtifactURLs}]}
config: {get_file: ./deploy-artifacts.sh}
outputs:
OS::stack_id:
description: The ID of the DeployArtifacts resource.
value: {get_resource: DeployArtifacts}