CI secrets - per-secret variable configuration
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Background
GitLab currently supports fetching secrets from HashiCrop Vault in pipelines via the secrets keyword in .gitlab-ci.yml. However, the configuration does not include options for URL, role, path or namespace. These are instead defined as general variables and thus the same for all secrets (VAULT_SERVER_URL, VAULT_AUTH_ROLE, VAULT_AUTH_PATH and VAULT_NAMESPACE).
Proposal
It would be beneficial if one could configure url, role, path and namespace for each secret in secrets separately, as secrets can exist in multiple vault instances, be accessible by policies of different roles, require login in different auth backends, or be in different namespaces.