Bug 1042225 - [RFE][heat]: Property status attributes for deprecation
Summary: [RFE][heat]: Property status attributes for deprecation
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/heat...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 21:27 UTC by RHOS Integration
Modified: 2015-03-19 17:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:22:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 21:27:15 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/property-schema-status.

Description:

It should be possible to mark a resource property as deprecated, or possibly a number of other statuses including:
* deprecated
* experimental
* GA (generally available, the default)
* non-standard (for heat extension properties on AWS resources)

Along with the status, the following would also be useful:
* status_reason - description providing some context for the status, such as the what the alternative is for deprecated properties
* status_version - the heat release where the property moved into the status (eg 2013.2). For GA properties we could write a script which trawls git history and identifies what release each property was added in

This information will be consumed by:
* template guide resource type doc generation
* resource_type API

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.