Heat Resource Type Versions

Registered by Julian Sy on 2016-11-09

Heat Resource types can have a version property so that we can support multiple versions across deployments. Resource types could have a default version, and if it's not provided the default would be used.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Julian Sy
Direction:
Needs approval
Assignee:
Julian Sy
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
milestone icon next

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.