Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1424600

Summary: [backport] --format json doesn't work since python-heatclient 0.8.0
Product: Red Hat OpenStack Reporter: Zane Bitter <zbitter>
Component: python-heatclientAssignee: Crag Wolfe <cwolfe>
Status: CLOSED ERRATA QA Contact: Amit Ugol <augol>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: achernet, aguetta, cwolfe, dcadzow, ddomingo, jruzicka, mburns, pablo.iranzo, rhel-osp-director-maint, shardy, srevivo, ukalifon, zbitter
Target Milestone: z3Keywords: FeatureBackport, Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: python-heatclient-1.5.0-2.el7ost Doc Type: Bug Fix
Doc Text:
Previously, running 'heat output-show' with the '--format json' option only showed the output value instead of the entire output definition (which included the description). As a result, it was not possible to use the CLI to get all of the data returned by the underlying API. With this update, the '--format json' option will now pass all data returned by the underlying API.
 Story Points: ---
Clone Of: 1421683 Environment:
Last Closed: 2017-06-28 15:25:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1421683    
Bug Blocks: 1424597    

Description Zane Bitter 2017-02-17 18:27:17 UTC 
+++ This bug was initially created as a clone of Bug #1421683 +++

Fix "heat output-show -F json" output format

So that it matches the equivalent OSC command's output. 
Also change the default output-show format to 'raw' to maintain current behavior.

Upsteam bug: https://bugs.launchpad.net/python-heatclient/+bug/1560087


Additional info:
Fix released for RHOS 11.
Comment 1 Zane Bitter 2017-02-28 19:38:50 UTC 
*** Bug 1425733 has been marked as a duplicate of this bug. ***
Comment 5 errata-xmlrpc 2017-06-28 15:25:46 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/RHBA-2017:1589