Project

General

Profile

Actions
Copy link

action #167641

open

coordination #154768: [saga][epic][ux] State-of-art user experience for openQA

coordination #154771: [epic] Improved test developer user experience

Clarify/simplify openqa-cli with "+VAR=..." usage

Added by okurz 4 months ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
QA (public) - future
Start date:
2024-09-30
Due date:
% Done:

0%

Estimated time:

Description

Motivation

From https://suse.slack.com/archives/C02CANHLANP/p1727700263544619 involving okurz and mpagot it became clear that the usage of +VAR for setting and overriding variable precendence is either quite complicated or not possible at all:

(okurz) Try +VAR=
(B) openqa-cli ... +_SECRET_SOMETHING=...yields Unknown option: _SECRET_SOMETHING
Credit to acarvajal for the workaround openqa-cli api ... -X POST isos -- +VAR=111

Not yet clear if that takes the variable with precedence

Acceptance criteria

  • AC1: openQA jobs can be scheduled with value precedence using openqa-cli
  • AC2: There is an obvious way how to set variables like +VAR

Suggestions

  • Prevent the argument parser to read those arguments starting with + or at least improve error handling and give a hint
  • Review documentation and help
Actions
Copy link
 #1

Updated by okurz 4 months ago

  • Tracker changed from coordination to action
Actions
Copy link

Also available in: Atom PDF