We used to validate intrinsic functions in the ResourceDefinition by just
passing it to function.validate(). That worked when it also acted as a
CloudFormation template snippet but, since that behaviour was removed by
2c6fc7bcd6b280a85488b0f32f8db7c7835f8b5c, that call now does nothing. This
replaces it with a validate() method on the ResourceDefinition itself.
This also improves path reporting for validation errors in deletion or
update policies.
Reviewed: https:/ /review. openstack. org/520831 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=316b80e1d51 cafb3beeab40866 4775c825febe17
Committed: https:/
Submitter: Zuul
Branch: master
commit 316b80e1d51cafb 3beeab408664775 c825febe17
Author: Zane Bitter <email address hidden>
Date: Thu Nov 16 18:17:23 2017 -0500
Ensure the whole ResourceDefinition is validated
We used to validate intrinsic functions in the ResourceDefinition by just validate( ). That worked when it also acted as a 280a85488b0f32f 8db7c7835f8b5c, that call now does nothing. This
passing it to function.
CloudFormation template snippet but, since that behaviour was removed by
2c6fc7bcd6b
replaces it with a validate() method on the ResourceDefinition itself.
This also improves path reporting for validation errors in deletion or
update policies.
Change-Id: I58c788002136dd f9bded309366e20 72823b3ac77
Closes-Bug: #1732798