Skip to content

Backend: Set variables as raw in Project->pipelines/new

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Currently, the majority of variables sent by GitLab to Runner are subject to variable expansion and does not support special characters such as $. When users add a variable value with $ (which is very common for generated passwords), the value is treated as a variable reference, which isn't expected behavior.

Users find it surprising that the variable gets expanded by default when the value contains a $. Often times the value is machine generated and might contain a $ to make it more secure.

Proposal

This issue is to make it possible to set variables as non-expanded in the Manual Job->Play page

Screen_Shot_2022-05-16_at_1.57.07_PM

Implementation Table

Group Issues Issue Link Notes
backend Backend: Make it possible to set variables as non-expanded in CI/CD Settings > Variables #361934 (closed) MVC
backend Backend: Backend: Make it possible to set a raw variable in our syntax #353991 (closed) MVC
frontend Frontend: Make it possible to set variables as non-expanded in CI/CD Settings > Variables #217309 (closed) MVC
backend Backend: Allow special characters to be used for raw variable types #352657 (closed) MVC
backend Backend: Make it possible to set variables as non-expanded in Project->pipelines/new 👈 You are here TBD at a later date
backend Backend: Make it possible to set variables as non-expanded in Manual Job->Play #362548 TBD at a later date
backend Backend: Make it possible to set variables as non-expanded in Project->pipeline_schedules/new #362549 TBD at a later date

Links/References

Edited by 🤖 GitLab Bot 🤖