adds support for per-branch variables: VARNAME@branch
What does this MR do?
Relaxes validation on variable keys to allow optional @branch suffix.
Are there points in the code the reviewer needs to double check?
No.
Why was this MR needed?
Together with gitlab-ci-multi-runner patch this allows definition of per-branch secret variables.
For example having
VAULT_PASS@master=abc VAULT_PASS@production=def
will expose VAULT_PASS=def when running on production branch.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together