API to get template version of any built-in resource

Registered by Steven Hardy on 2013-05-01

From: http://lists.openstack.org/pipermail/openstack-dev/2013-April/007989.html

* Add an API to get a generic template version of any built-in resource (with all properties/outputs defined) that can be easily
customised to make a new provider template.

Blueprint information

Status:
Complete
Approver:
Steven Hardy
Priority:
High
Drafter:
None
Direction:
Approved
Assignee:
andrew plunk
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
andrew plunk on 2013-07-08
Completed by
Steven Dake on 2013-08-13

Related branches

Sprints

Whiteboard

Add an API endpoint of the following form:

/v1/{tenant_id}/resources_types/{type_name}/providers/{provider}/template

with an alias for the default provider at:

/v1/{tenant_id}/resources_types/{type_name}/template

For an uploaded provider template, the API should just return the template.

For a resource plugin, the API should return a provider template that is a straight pass-through to the underlying resource. All of the properties of the underlying resource should be obtained from the template parameters, and all of its Fn::GetAttr values and it's Ref value exposed as stack outputs.

Gerrit topic: https://review.openstack.org/#q,topic:bp/resource-template,n,z

Addressed by: https://review.openstack.org/36844
    Generate a template from a resource implementation.

Gerrit topic: https://review.openstack.org/#q,topic:bp/resource-data,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bug/1197747,n,z

Addressed by: https://review.openstack.org/38643
    Generate a template from a resource implementation.

Addressed by: https://review.openstack.org/38714
    Add rest endpoints for resource template generation.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.