action #86063
Updated by okurz over 3 years ago
## Motivation Most of openQA functionality is available over the webUI with prominent exceptions like "trigger tests". To allow easier workflows for web centric users or for easier integration into infrastructures where no custom "openQA client" can be called but only HTTP endpoints we should offer such possibility ## Acceptance criteria * **AC1:** openQA jobs with arbitrary parameters can be triggered over the webUI for authenticated users with right permissions (operator+) * **AC2:** openQA jobs can be triggered with single curl calls * **AC3:** All Generic openQA API calls with known exceptions can be conducted without needing an openQA CLI ## Suggestions e.g. a POST route where one can authenticate with username+password forwarded to any external authentication service or existing API key+secret. Within the webUI a POST request could be sent from an authenticated webUI form, e.g. a single simple textfield taking all parameters that the openQA CLIs would also take.