secret names should support all valid environment variable names

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

• Close this issue

Description

The problem is that Microsoft uses colon (:) in environment variable names in order to simulate a key hierarchy. This allows .NET to override deeply nested configuration with environment variables of the format PARENT:CHILD:LEAF = VALUE.

These names with colons are unsupported by gitlab secret variables so it's not possible to override configuration with environment variables controlled in gitlab secrets.

Proposal

If a string is a valid environment variable name, it should be able to be set as a gitlab secret key name.

Links / references

https://gitlab.com/gitlab-org/gitlab-ce/issues/31243 is related to a similar issue in the values.