For template-validate to use the normal stack.validate code instead
of reimplementing different validation logic, we need to disable
the resource plugin validate() methods, because in nearly all cases
these refer to resource property values, which don't exist at
template-validate time, where parameters aren't mandatory.
We do however want to ensure structural/syntax issues in the resource
definition are caught as early as possible, so add a stack
resource_validate attribute (defaulted to True) which enables selecting
only the resource.Resource superclass validate logic, so we can defer
the full value validation until create without maintaining completely
separate logic.
Reviewed: https:/ /review. openstack. org/223737 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=99ae1702ffa 6abcba909a2fb69 2b30163bcc8f5b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 99ae1702ffa6abc ba909a2fb692b30 163bcc8f5b
Author: Steven Hardy <email address hidden>
Date: Tue Sep 15 18:59:09 2015 +0100
Allow selectively disabling resource validation
For template-validate to use the normal stack.validate code instead validate time, where parameters aren't mandatory.
of reimplementing different validation logic, we need to disable
the resource plugin validate() methods, because in nearly all cases
these refer to resource property values, which don't exist at
template-
We do however want to ensure structural/syntax issues in the resource validate attribute (defaulted to True) which enables selecting
definition are caught as early as possible, so add a stack
resource_
only the resource.Resource superclass validate logic, so we can defer
the full value validation until create without maintaining completely
separate logic.
Change-Id: I501c8c36e923ba a8d9b3f0395aaee 41f7585ebb1
Partial-Bug: #1467573