Project

General

Profile

Actions

action #155473

closed

coordination #127031: [saga][epic] openQA for SUSE customers

coordination #80150: [epic] Scale out openQA: Easier openQA setup

Avoid the need for API keys within the same container/client

Added by livdywan 10 months ago. Updated 10 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2024-01-13
Due date:
% Done:

0%

Estimated time:

Description

Motivation

The conversion spurred by #153499#note-7 brought up the question why a newly created container with openQA webUI, worker and client would require the user to know about and manually configure API keys.

Acceptance criteria

  • AC1: It is possible to run the container without manually setting up API keys already known to openQA

Suggestions

  • Containers can be stopped and re-created all the time. Consider this for the user story
  • registry.opensuse.org/devel/openqa/containers/openqa-single-instance contains all the parts from webUI to client - the API key is known by design

Related issues 2 (0 open2 closed)

Copied from openQA Project (public) - action #153499: Ensure the openQA developer mode works straight-forward in the container setup when following our documentation size:MResolvedmkittler2024-01-13

Actions
Copied to openQA Project (public) - action #155491: Extend documentation for single-instance-container covering at least how to trigger/clone existing jobs size:SResolvedjbaier_cz2024-01-13

Actions
Actions

Also available in: Atom PDF