Heat should reserve the template keyword, stack-metadata, as a placeholder for assorted data.

Registered by Tim Schnell on 2013-10-31

There is a need to have a reserved namespace, stack-metadata, in each HOT template where non-heat specific data can be stored. This can be used as a place to put a template UUID, display hints, template release notes, etc... Heat should skip this section when it comes to parsing the template but essentially, store and ignore it.

Blueprint information

Status:
Complete
Approver:
Steve Baker
Priority:
Medium
Drafter:
Tim Schnell
Direction:
Approved
Assignee:
Tim Schnell
Definition:
Obsolete
Series goal:
None
Implementation:
Needs Code Review
Milestone target:
None
Started by
Tim Schnell on 2013-11-14
Completed by
Steve Baker on 2013-12-03

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/namespace-stack-metadata,n,z

Addressed by: https://review.openstack.org/56450
    Changes hot.py to reserve the template keyword stack_metadata

(stevebaker) Obsoleting this so that separate blueprints can be raised for individual HOT schema changes

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.