Bug 1142563

Summary:	[RFE][heat]: Detailed Resource Show
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-heat	Assignee:	Zane Bitter <zbitter>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	ddomingo, markmc, nbarcet, sbaker, shardy, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/heat/+spec/detailed-resource-show
Whiteboard:	upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-heat-2015.1.0-3.el7ost	Doc Type:	Enhancement
Doc Text:	When querying a resource in the Orchestration API, a user can now request the value of one or more of the resource's attributes be included in the output. This can aid debugging, as it allows the user to retrieve data from any resource at any time without having to modify the stack's template to include that data in the outputs section.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:13:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-09-17 04:03:37 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/detailed-resource-show.

Description:

After creating a stack, there is currently no way to retrieve a resource's
attributes other than outside of heat (e.g. a user can get the ID of a nova
server and call nova directly to get such attributes).

We propose returning all resource attributes when displaying data for a
specific resource.  This way, a user will be able to issue a resource-show call
and be able to look up attributes after creating their stacks even if the
template author didn't think about them beforehand.

Specification URL (additional information):

https://review.openstack.org/#/c/121979/

Comment 7 errata-xmlrpc 2015-08-05 13:13:56 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2015:1548