39a5545c41
Those are hidden resource types in heat. Changing these types would not result in replacement of the resources. Change-Id: I22d23a8f187263bd36e364f0cd3301c830f3220b
43 lines
1.3 KiB
YAML
43 lines
1.3 KiB
YAML
heat_template_version: rocky
|
|
|
|
description: >
|
|
Example extra config for post-deployment, this re-runs every update
|
|
|
|
# Note extra parameters can be defined, then passed data via the
|
|
# environment parameter_defaults, without modifying the parent template
|
|
parameters:
|
|
servers:
|
|
type: json
|
|
# This is provided via parameter_defaults from tripleoclient
|
|
# it changes to a new timestamp every update, so we can use it to
|
|
# trigger the deployment to run even though it and the config are
|
|
# otherwise unchanged
|
|
DeployIdentifier:
|
|
type: string
|
|
default: ''
|
|
description: >
|
|
Setting this to a unique value will re-run any deployment tasks which perform configuration on a Heat stack-update.
|
|
|
|
resources:
|
|
|
|
ExtraConfig:
|
|
type: OS::Heat::SoftwareConfig
|
|
properties:
|
|
group: script
|
|
inputs:
|
|
- name: deploy_identifier
|
|
config: |
|
|
#!/bin/sh
|
|
echo "extra_update $deploy_identifier" >> /root/extra_update
|
|
|
|
ExtraDeployments:
|
|
type: OS::Heat::SoftwareDeploymentGroup
|
|
properties:
|
|
name: ExtraDeployments
|
|
servers: {get_param: servers}
|
|
config: {get_resource: ExtraConfig}
|
|
# Do this on CREATE/UPDATE (which is actually the default)
|
|
actions: ['CREATE', 'UPDATE']
|
|
input_values:
|
|
deploy_identifier: {get_param: DeployIdentifier}
|