QA » openQA Project » openQA Tests » qe-yam

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