Bug 1042225

Summary: [RFE][heat]: Property status attributes for deprecation
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/heat/+spec/property-schema-status
Whiteboard: upstream_milestone_none upstream_status_implemented upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:22:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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