Project

General

Profile

Actions
Copy link

action #160334

open

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

[qe-core] Add CI/CD check to avoid uses of nots3cr3t or other hardcoded password in pull requests

Added by szarate 2 months ago. Updated about 1 month ago.

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Infrastructure
Target version:
QA - QE-Core: Ready
Start date:
2024-05-14
Due date:
% Done:

0%

Estimated time:
Difficulty:
Sprint:
QE-Core: May Sprint 24 (May 07 - Jun 04)
Tags:
security, password, qe-core-may-sprint

Description

Motivation

In https://sd.suse.com/servicedesk/customer/portal/1/SD-150437 we are asked to handle "compromised root passwords in QA segments"

This will not stop somebody from adding a different password though, so we need to think a bit before working on this, however we can start with using it on the data directory first.

Related issues 2 (1 open — 1 closed)

Related to openQA Tests - coordination #96596: [qe-core][CI] CI/CD and Coding style improvementsBlockedszarate2019-12-11

Actions
Related to openQA Tests - action #160325: [qe-core] Use templating system in autoyast profiles to use testapi::$password instead of nots3cr3tResolvedrfan12024-05-14

Actions
Actions
Copy link
 #1

Updated by szarate 2 months ago

Actions
Copy link
 #2

Updated by szarate 2 months ago

  • Related to action #160325: [qe-core] Use templating system in autoyast profiles to use testapi::$password instead of nots3cr3t added
Actions
Copy link
 #3

Updated by szarate 2 months ago

  • Sprint set to QE-Core: May Sprint 25 (May 07 - Jun 04)
Actions
Copy link
 #4

Updated by szarate about 1 month ago

  • Status changed from New to In Progress
Actions
Copy link
 #5

Updated by szarate about 1 month ago

  • Status changed from In Progress to Workable
Actions
Copy link
 #6

Updated by szarate about 1 month ago

  • Priority changed from Normal to Low
Actions
Copy link

Also available in: Atom PDF