From 12576925fa466e461285aadc9ec2a00a8ff3e54f Mon Sep 17 00:00:00 2001 From: Steven Hardy Date: Wed, 17 May 2017 15:33:55 +0100 Subject: [PATCH] Reference SoftwareDeploymentGroup resource The old name for this was SoftwareDeployments, but this causes confusion due to the similarity with SoftwareDeployment, so update to the new, clearer, name. Change-Id: Ia29a1c9fd9a404a34eab34ad40a85f257c3b0a65 --- doc/source/advanced_deployment/extra_config.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/advanced_deployment/extra_config.rst b/doc/source/advanced_deployment/extra_config.rst index 7aeb34be..8d8e6a62 100644 --- a/doc/source/advanced_deployment/extra_config.rst +++ b/doc/source/advanced_deployment/extra_config.rst @@ -225,7 +225,7 @@ Below is an example of a post-deployment configuration template:: _APARAM_: {get_param: some_extraparam} ExtraDeployments: - type: OS::Heat::SoftwareDeployments + type: OS::Heat::SoftwareDeploymentGroup properties: servers: {get_param: servers} config: {get_resource: ExtraConfig} @@ -246,7 +246,7 @@ environment which enables the configuration. unintended reuse of parameter names between multiple templates, because parameter_defaults is applied globally. -The "actions" property of the `OS::Heat::SoftwareDeployments` resource may be +The "actions" property of the `OS::Heat::SoftwareDeploymentGroup` resource may be used to specify when the configuration should be applied, e.g only on CREATE, only on DELETE etc. If this is omitted, the heat default is to apply the config on CREATE and UPDATE, e.g on initial deployment and every subsequent