Actions
action #34492
closed[functional][sle][y] How to handle leaked SCC regcodes, e.g. on github?
Start date:
2018-04-08
Due date:
% Done:
0%
Estimated time:
Description
Motivation¶
For our SLE tests we use SCC regcodes which are commonly stored in openQA settings, that is in the internal database and therefore considered on a limited location staying within the trusted business. However, sometimes someone messes up and mentions a regcode in e.g. this ticket tracker itself which is public by default or on github. We should find a workflow how to handle these cases.
Acceptance criteria¶
- AC1: The workflow for leaked reg codes is documented, e.g. on the README of os-autoinst-distri-opensuse
Suggestions¶
- Ask SCC experts, e.g. on the suse#happy-customer IRC channel how to handle these cases
- Incorporate the feedback into proper documentation, e.g. the README of os-autoinst-distri-opensuse
- Try to prevent the leaking by automatic checks, e.g. a pre-push git hook
Updated by okurz almost 6 years ago
- Target version changed from Milestone 17 to future
Updated by okurz almost 6 years ago
- Target version changed from future to future
Updated by riafarov over 3 years ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Enhancement to existing tests) - Status changed from Workable to Closed
- Assignee set to riafarov
Updated by riafarov about 3 years ago
- Target version changed from future to SLE 15 SP3
Actions