Secrets in their own project
vela cannot stop git clone. To keep a folder out of some people's clones, move it into a separate GitLab project and include it as a submodule.
vela cannot stop git clone (see the README). If a folder
must stay secret from some people who can clone the main project, move it into a separate project and
include it as a submodule. GitLab then checks access on the secret project itself, using its normal permissions.
- Create a project, for example
myapp-secrets, and give access only to the people who need it. - Move the folder's history into it (keep history with
git filter-repo --path secrets/ --path-rename secrets/:) or just copy the files if the history is not needed. - In the main project:
git rm -r secrets && git submodule add git@gitlab.example.com:group/myapp-secrets.git secrets, then commit. - People without access to
myapp-secretssee an emptysecrets/folder aftergit submodule update; the clone never contained the files.
Remove the old files from history too. Anyone who already cloned, and every old commit, still has them. Rewrite
the history of the main project (git filter-repo --path secrets/ --invert-paths), rotate any secret that was in it,
and ask everyone to re-clone.
Trade-offs: two projects to manage, and a change spanning both needs two merge requests. In return, hiding is real.
This page is built from docs/split-secrets.md on GitHub.
Encrypted paths (Tier C)
Tier C stores files under protected folders encrypted to SSH keys, so a clone holds ciphertext. Setup, what other users get, and what does not work.
Compatibility results
Which GitLab CE versions vela is tested on: live results for the server hook and the overlay on 15.11 to 19.5, the upgrade test, and what is not tested.