Consider displaying stack outputs all the time

Bug #1537693 reported by Thomas Herve on 2016-01-25
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Thomas Herve

Bug Description

This is mostly a request for feedback. Current we don't return stack outputs if the status is IN_PROGRESS, but I think we should. This is an useful interface for users, and I'm not sure how we're protecting them by not returning them at all, instead of giving what we have.

If there is an reason, I'd like to know it, otherwise we should expose them all the time.

Joe D'Andrea (joedandrea) wrote :

+1. Yes, please. Agreed on all counts.

Steve Baker (steve-stevebaker) wrote :

Totally agree - I thought I might have raised a bug for this ages ago, or maybe I just wish I had.

Changed in heat:
status: New → Triaged
Amit Ugol (amit-ugol) wrote :

From QA POV, +3
But needs some thinking about implementation and how it looks.

Fix proposed to branch: master

Changed in heat:
status: Triaged → In Progress

Submitter: Jenkins
Branch: master

commit 76663a26d996911f5d41ade65e44dd11f5d83e0e
Author: Thomas Herve <email address hidden>
Date: Tue Jan 26 09:17:30 2016 +0100

    Return stack outputs when in progress

    Don't filter out stack outputs when stack status is in progress,
    returning it all the time instead.

    Change-Id: Ife8f1eafe85e9ff4ce5f0a4692c64343c1c2d0b4
    Closes-Bug: #1537693

Changed in heat:
status: In Progress → Fix Released

This issue was fixed in the openstack/heat development milestone.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers