Removing no-ops from plan only will have no effect, we need to let
Heat know about the no-ops removal too. Client commands always fully
recreate the plan in swift, so any plan edits need to be immediately
applied.
For the same reason this commit also drops execution of the workfow --
so far we thought it's just superfluous (does what the env file did),
but in fact can't have any effect at all, so let's not execute that
code at all.
Reviewed: https:/ /review. openstack. org/565828 /git.openstack. org/cgit/ openstack/ python- tripleoclient/ commit/ ?id=a0006df5442 ee94637f236c46c f1a0fb436e5c0a
Committed: https:/
Submitter: Zuul
Branch: master
commit a0006df5442ee94 637f236c46cf1a0 fb436e5c0a
Author: Jiri Stransky <email address hidden>
Date: Wed May 2 17:58:58 2018 +0200
Update Heat stack on update/upgrade/ffwd converge
Removing no-ops from plan only will have no effect, we need to let
Heat know about the no-ops removal too. Client commands always fully
recreate the plan in swift, so any plan edits need to be immediately
applied.
For the same reason this commit also drops execution of the workfow --
so far we thought it's just superfluous (does what the env file did),
but in fact can't have any effect at all, so let's not execute that
code at all.
Depends-On: I9039db99f43e8a d091ea6fef7e3a1 49fcddf1334 e33bb64cfc3f306 3b6a5528cc6
Change-Id: Ife57bfae034f70
Closes-Bug: #1768586