Project

General

Profile

Actions
Copy link

coordination #162080

open

coordination #105624: [saga][epic] Reconsider how openQA handles secrets

[epic] Hide SCC regcodes like secrets and passwords

Added by okurz 7 months ago. Updated about 1 month ago.

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

0%

Estimated time:
(Total: 0.00 h)

Description

Motivation

os-autoinst+openQA support to hide secrets if test variables are called accordingly but SCC regcodes are still being leaked to the public from time to time due to the test variables not matching the default patterns. It was already suggested to change the test variable names but this hasn't happened yet and is not progressing. See #156235 as well as #109019 for context. Let's add support to configure which test variables are treated as secret.

Subtasks 5 (5 open — 0 closed)

action #138653: Ensure our handling of "secrets", i.e. _SECRET variables, is documentedNew2024-11-26

Actions
action #162083: os-autoinst support for custom secret hidingNewokurz2024-06-11

Actions
action #162086: openQA support for custom secret hidingNew2024-06-11

Actions
action #162089: Hide SCC regcodes from OSD tests, e.g. SCC_REGCODENew2024-06-11

Actions
action #170308: Secret handling doesn't scrub values from logs and/or result filesNew2024-11-26

Actions
Actions
Copy link
 #1

Updated by okurz 7 months ago

  • Subtask #138653 added
Actions
Copy link
 #2

Updated by okurz 7 months ago

  • Subtask #162083 added
Actions
Copy link
 #3

Updated by okurz 7 months ago

  • Subtask #162086 added
Actions
Copy link
 #4

Updated by okurz 7 months ago

  • Subtask #162089 added
Actions
Copy link
 #5

Updated by okurz about 1 month ago

  • Subtask #170308 added
Actions
Copy link

Also available in: Atom PDF