Handle HOT param constraints in provider templates
When HOT templates are used as provider templates, parameter constraints
have to be translated into provider resource properties correctly. The
properties Schema class has been design to cover both CFN and HOT, but
the code in Schema.from_parameter has to distinguish between CFN and
HOT parameter constraints to correctly build the schema.
Reviewed: https:/ /review. openstack. org/47877 github. com/openstack/ heat/commit/ c8293a3143c7a11 e7c9d922797f479 43e04c9d50
Committed: http://
Submitter: Jenkins
Branch: master
commit c8293a3143c7a11 e7c9d922797f479 43e04c9d50
Author: Thomas Spatzier <email address hidden>
Date: Mon Sep 23 18:47:42 2013 +0200
Handle HOT param constraints in provider templates
When HOT templates are used as provider templates, parameter constraints from_parameter has to distinguish between CFN and
have to be translated into provider resource properties correctly. The
properties Schema class has been design to cover both CFN and HOT, but
the code in Schema.
HOT parameter constraints to correctly build the schema.
This patch fixes the handling of HOT parameters.
Change-Id: I59027d3b51e5d6 dcc2a867cc5b501 5cd6c88051c
Closes-Bug: #1224111