There's no reason to not issue an update to a nested stack, so don't bother
trying to decide if its inputs have changed (and especially don't replace
it because it's in a failed state).
Change-Id: Ia48ebfcb6c1b3a904f01a83f8f34d8c7a13bb2be
Related-Bug: #1383618
(cherry picked from commit 35ac781db3d529317bac691eae3fb08d208d1e56)
Reviewed: https:/ /review. openstack. org/145332 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=d8abdfd34ff 089d0173da525da 03cfbb20412c83
Committed: https:/
Submitter: Jenkins
Branch: stable/juno
commit d8abdfd34ff089d 0173da525da03cf bb20412c83
Author: Zane Bitter <email address hidden>
Date: Fri Dec 12 15:20:24 2014 -0500
Always update nested stacks
There's no reason to not issue an update to a nested stack, so don't bother
trying to decide if its inputs have changed (and especially don't replace
it because it's in a failed state).
Change-Id: Ia48ebfcb6c1b3a 904f01a83f8f34d 8c7a13bb2be 17bac691eae3fb0 8d208d1e56)
Related-Bug: #1383618
(cherry picked from commit 35ac781db3d5293