3c6ec654b4
Heat now supports release name aliases, so we can replace the inconsistent mix of date related versions with one consistent version that aligns with the supported version of heat for this t-h-t branch. This should also help new users who sometimes copy/paste old templates and discover intrinsic functions in the t-h-t docs don't work because their template version is too old. Change-Id: Ib415e7290fea27447460baa280291492df197e54
33 lines
1.1 KiB
YAML
33 lines
1.1 KiB
YAML
heat_template_version: ocata
|
|
|
|
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}
|