Abstract resource templates out of resources
Each resource is defined with a snippet out of a larger template. Currently this exists in the literal form of a snippet out of a larger template, with the result that the Resource class and its subclasses are directly reading the template data. This is not conducive to supporting two or more different template formats (i.e. CloudFormation and HOT). We need to create a separate ResourceTemplate class with its own API that resources can access. There would be HOT and CloudFormation versions of this class.
It would also be extremely helpful if ResourceTemplates are both comparable (for things like updates) and hashable (for things like https:/
This should also make it easier to do things like building templates on the fly, which is done now by the autoscaling code and will be done in the future during stack updates.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- Zane Bitter
- Direction:
- Approved
- Assignee:
- Zane Bitter
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Zane Bitter
- Completed by
- Zane Bitter
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add a ResourceDefinition class
Work Items
Dependency tree
* Blueprints in grey have been implemented.
