commit 0f58b65e19b2dc1546239da24cc7fde927f2a727
Author: Thomas Spatzier <email address hidden>
Date: Fri Feb 6 16:33:29 2015 +0100
Always check for 'component' in SoftwareDeployment
When SoftwareDeployment is associated to a SoftwareComponent, config
hooks in the instance should always be trigger and the in-instance
logic will decide whether or not anything has to be done.
The check whether the SoftwareDeployment resource is associated to a
SoftwareComponent resource is implemented in _handle_action which is
called by all handle_ methods.
For handle_delete, however, the 'actions' property of
SoftwareDeployment was evaluated first and only if it contained
DELETE the _handle_action method was invoked.
This patch make handle_delete also directly call _handle_action to
check for presence of a SoftwareComponent like all other lifecycle
hooks do.
Reviewed: https:/ /review. openstack. org/153604 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=0f58b65e19b 2dc1546239da24c c7fde927f2a727
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0f58b65e19b2dc1 546239da24cc7fd e927f2a727
Author: Thomas Spatzier <email address hidden>
Date: Fri Feb 6 16:33:29 2015 +0100
Always check for 'component' in SoftwareDeployment
When SoftwareDeployment is associated to a SoftwareComponent, config
hooks in the instance should always be trigger and the in-instance
logic will decide whether or not anything has to be done.
The check whether the SoftwareDeployment resource is associated to a ponent resource is implemented in _handle_action which is loyment was evaluated first and only if it contained
SoftwareCom
called by all handle_ methods.
For handle_delete, however, the 'actions' property of
SoftwareDep
DELETE the _handle_action method was invoked.
This patch make handle_delete also directly call _handle_action to
check for presence of a SoftwareComponent like all other lifecycle
hooks do.
Change-Id: Ibb813db23fa7c9 ab20435887f6cc4 9deaaf51de2
Closes-Bug: #1416994