Code-completion support for secrets in pipeline editor
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Context
Currently, developers need to manually copy and paste secret keys when configuring pipelines in the editor. This process can be time-consuming and can introduce errors. Providing code-completion support for secrets would streamline the workflow, making it easier for users to adopt Secrets Manager and integrate secrets into their development processes.
Problem to solve
- Minimise time spent finding and typing secret keys manually.
- Integrate secrets into developer workflows makes it easier for users to adopt the Secrets Manager.
- Reduces friction for developers by aligning with the coding experiences.
Proposal
- Auto-suggest secret keys within pipelines and scripts
- Display relevant secret keys or parameters when users are writing YAML files or pipeline configurations.
- In Pipeline Editor, code-completion suggests secret keys when users type the keyword
secrets.(TBC). A modal pops up, offering secret keys for insertion into the code.
Related links:
Edited by 🤖 GitLab Bot 🤖
