Add a heat.type constraint

Bug #1545857 reported by Jay Dobies on 2016-02-15
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Jay Dobies

Bug Description

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.

Jay Dobies (jdob) on 2016-02-15
Changed in heat:
assignee: nobody → Jay Dobies (jdob)
Sergey Kraynev (skraynev) wrote :

+1 from me for this idea

Changed in heat:
milestone: none → mitaka-3
importance: Undecided → Wishlist

Fix proposed to branch: master

Changed in heat:
status: New → In Progress
Changed in heat:
milestone: mitaka-3 → newton-1
Rabi Mishra (rabi) on 2016-06-01
Changed in heat:
milestone: newton-1 → newton-2

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

Changed in heat:
status: In Progress → Fix Released

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers