Currently we pass the template value directly into ResourceDefinition
which can result in an assertion error from the constructor in the
stack.Stack.validate path. We can avoid this by explicitly translating
the expected policies for each template dialect into the keys
supported by the resource definition.
Reviewed: https:/ /review. openstack. org/224292 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=92bf3aa5dcf 04d6d653174d349 7de00a8b5c518b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 92bf3aa5dcf04d6 d653174d3497de0 0a8b5c518b
Author: Steven Hardy <email address hidden>
Date: Wed Sep 16 21:38:47 2015 +0100
Validate deletion policy during template parsing
Currently we pass the template value directly into ResourceDefinition Stack.validate path. We can avoid this by explicitly translating
which can result in an assertion error from the constructor in the
stack.
the expected policies for each template dialect into the keys
supported by the resource definition.
Change-Id: I54de89ec6b7cd4 af722c9c2635772 52c15aaad64
Closes-Bug: #1496502