馃帹 Design: Credential variable for CI/CD jobs
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Background
This is an idea that came from this thread discussion:
As a user (Developer Role), I am responsible for creating/manage security scan job (Such as fuzz testing), sometimes, I need to add test account credentials to the scan jobs. The credentials can be reused and should be masked in yml file. But if I use CI-variables, I need to ask a team member who is a maintainer to put the credential in the scans before I start it and do other types of fine-tuning. Since credentials are test account, I should have access to use them, at least select them from a list.
Potential solutions
Since credential sets might use a different purpose and maybe need a different technical solution. We can separate variables into two groups: environmental variables and credentials variables
The pictures below are just quick idea illustrations for future discussion
Besides current
| Overview | Details |
|---|---|
 |
 |