Introduce a schema for attributes

Registered by Steven Hardy on 2013-05-01

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

Introduce a schema for attributes (i.e. allowed arguments to Fn::GetAttr)

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
Randall Burt
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Randall Burt on 2013-06-05
Completed by
Randall Burt on 2013-06-20

Related branches

Sprints

Whiteboard

Resource properties have a schema, but currently the valid arguments to Fn::GetAttr do not. We need to add a schema so that we can autogenerate documentation from the resource types, and also so that we can generate a skeleton provider template with the correct outputs defined so that Fn::GetAttr can read directly from the provider template outputs.

The schema will probably take a similar form to the properties schema: an attribute (sorry) on the Resource subclass. However, it can be substantially simpler as the output of Fn::GetAttr is always implicitly a string.

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

Addressed by: https://review.openstack.org/32216
    Introduce a schema for attributes

Addressed by: https://review.openstack.org/32933
    Implement attribute schema for resources

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.