Bug 1697379

Summary: RFE: add --wait flag to compose sub command
Product: Red Hat Enterprise Linux 8 Reporter: Fred van Zwieten <fvzwieten>
Component: loraxAssignee: Brian Lane <bcl>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team>
Severity: unspecified Docs Contact: Eliane Ramos Pereira <elpereir>
Priority: unspecified    
Version: 8.0CC: elpereir
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-21 21:15:04 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:

Description Fred van Zwieten 2019-04-08 12:46:59 UTC 
Description of problem:
When composing an image using the compose-cli, the request is put in the queue. When using composer-cli in a scripted use-case (or ansible) one would like to wait until the image has been composed before continuing in the script.

Suggestion: composer-cli compose start <blueprint> --wait

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Brian Lane 2019-04-09 15:26:00 UTC 
The composer-cli utility really isn't meant to be used from scripts. The ui isn't stable and may change at any time, and the output is for humans, not scripts (despite having the --json option which was more for debugging than anything).

If you are scripting use of the API you should really talk to the socket directly, not call composer-cli. It's fairly easy to do using python.

That being said, I can see a --wait option being useful for humans, so I'll add it to the list.
Comment 2 Brian Lane 2019-10-21 21:15:04 UTC 
Needs to be done upstream first: https://github.com/weldr/lorax/issues/685