Introduce a schema for attributes
From: http://
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:
-
2013.2
- Started by
- Randall Burt
- Completed by
- Randall Burt
Related branches
Related bugs
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:/
Addressed by: https:/
Introduce a schema for attributes
Addressed by: https:/
Implement attribute schema for resources
Work Items
Dependency tree
* Blueprints in grey have been implemented.
