Actions
action #90038
closedcoordination #127031: [saga][epic] openQA for SUSE customers
coordination #80150: [epic] Scale out openQA: Easier openQA setup
Better error handling when reading API key+secret from ~/.config/openqa/client.conf
Start date:
2021-03-12
Due date:
% Done:
0%
Estimated time:
Description
Observation¶
With a file like ~/.config/openqa/client.conf with slightly incorrect format and names used because the user does not know any better:
[openqa.opensuse.org]
apikey = FOO
apisecret = BAR
$ openqa-clone-job --skip-chained-deps --within-instance https://openqa.opensuse.org/tests/1234
Use of uninitialized value $val in substitution (s///) at /usr/share/openqa/script/../lib/OpenQA/UserAgent.pm line 46.
Use of uninitialized value $val in substitution (s///) at /usr/share/openqa/script/../lib/OpenQA/UserAgent.pm line 46.
Failed to create job: "{\"error\":\"no api key\",\"error_status\":403}" at /usr/bin/openqa-clone-job line 304.
Acceptance criteria¶
- AC1: No low-level perl warnings on incorrect usage or user mistakes
- AC2: There is help accessible from command line explaining the right format for the config file
- AC3: More helpful error message
Actions