Add a heat.type constraint

[Jay Dobies]

Resource chains allow one or more resources to be created in a nested stack. The types of resources created are specified as an input to the chain and often specified through a template parameter.

This spec is intended as a way for clients to identify which parameters are used in this fashion. The approach is to add a new custom constraint 'heat.type' to let Heat validate that the list of values in the parameter are all resolvable Heat resource types.

[Sergey Kraynev (skraynev)]

+1 from me for this idea

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/284960

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/284960
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=f5c32ad8fda3d7dcee6e4f9447621cde6d0f8a01
Submitter: Jenkins
Branch: master

commit f5c32ad8fda3d7dcee6e4f9447621cde6d0f8a01
Author: Jay Dobies <email address hidden>
Date: Thu Feb 25 17:03:01 2016 -0500

    Added heat.resource_type custom constraint

    This constraint will validate that a parameter value is a valid resource
    type within the context of the template (that is, taking into account
    the environment file(s) passed in as well).

    Change-Id: I82b18d52982c2731370df9ea4ea0e398bf7702f2
    Closes-Bug: #1545857

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/heat 7.0.0.0b2 development milestone.