Don't always validate heat stack when adding parameters
There are certain cases we add parameters to plan environment
when creating and updating a plan. As part of that action we
aslo try to validate the stack/template. However, validation
would fail, if we've resource mappings in user-environment that
are not merged/added to the plan yet.
This adds new input flag to plan create and update workflows which
can then be changed in python-tripleoclient, so as not to imapct the
UI workflows.
Reviewed: https:/ /review. openstack. org/639072 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=762bf8c9e7b cfbbc4b6682e5f7 c6347e213ad622
Committed: https:/
Submitter: Zuul
Branch: master
commit 762bf8c9e7bcfbb c4b6682e5f7c634 7e213ad622
Author: Rabi Mishra <email address hidden>
Date: Thu Feb 21 17:34:17 2019 +0530
Don't always validate heat stack when adding parameters
There are certain cases we add parameters to plan environment
when creating and updating a plan. As part of that action we
aslo try to validate the stack/template. However, validation
would fail, if we've resource mappings in user-environment that
are not merged/added to the plan yet.
This adds new input flag to plan create and update workflows which tripleoclient, so as not to imapct the
can then be changed in python-
UI workflows.
Change-Id: I9c54379925339e aaa9a0ee61cb823 bddc95737c7
Partial-Bug: #1817539