https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-01-12T16:47:27ZopenSUSE Project Management ToolopenQA Project - action #87647: openqa-cli api ignores extra argumentshttps://progress.opensuse.org/issues/87647?journal_id=3773542021-01-12T16:47:27Zkraihsebastian.riedel@suse.com
<ul></ul><p>Might be reasonable to make it die with a good error message. Makes it easier to convert from client to openqa-cli.</p>
openQA Project - action #87647: openqa-cli api ignores extra argumentshttps://progress.opensuse.org/issues/87647?journal_id=3775042021-01-13T09:19:55Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> set to <i>future</i></li></ul><p>Would be nice to improve that. I would not be concerned with "backward compatibility" within openqa-cli as the new tool. For our "old, deprecated, obsolete use cases" we still have "openqa-client" :)</p>
openQA Project - action #87647: openqa-cli api ignores extra argumentshttps://progress.opensuse.org/issues/87647?journal_id=5032732022-03-22T17:39:00Zokurzokurz@suse.com
<ul></ul><p>Can you be more specific about the expected cases and the actual cases? When I call <code>openqa-cli api --host https://openqa.opensuse.org assets</code> I get a huge list of assets. You want to filter that list or what? And when I call <code>openqa-cli api --host https://openqa.opensuse.org --foo</code> I get "Unknown option: foo", the complete usage information and a non-zero exit code. So that looks good so far.</p>
openQA Project - action #87647: openqa-cli api ignores extra argumentshttps://progress.opensuse.org/issues/87647?journal_id=5215432022-05-20T12:10:04Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>no response</p>