Issue: GitLab now supports fine-grained PATs, but the Flux documentation does not say exactly which of these fine-grained permissions a PAT needs in order to be used for Flux bootstrapping. Documentation like this exists for Gitea PATs and GitHub PATs, but not GitLab PATs.
Suggested Fix: The documentation for GitLab bootstrapping should explain exactly which permissions a fine-grained PAT needs in order to be used for bootstrapping Flux.
Based on my own experience, I believe the minimum permissions are:
- Projects > Project > Read
- Repository > Code > Download, Push
- System Access > Deploy Token > Create, Read, Delete
If somebody can confirm that all of the above are necessary, and that no further permissions are necessary for other Flux features that I happen to not be using, I'll go ahead and write up a PR.
Fine-grained permissions documentation may also be missing for bootstrapping on other platforms (Bitbucket, Azure, GCS, Oracle, etc.) but I'll leave any issue-creation for those platforms to whatever communities use them.
Issue: GitLab now supports fine-grained PATs, but the Flux documentation does not say exactly which of these fine-grained permissions a PAT needs in order to be used for Flux bootstrapping. Documentation like this exists for Gitea PATs and GitHub PATs, but not GitLab PATs.
Suggested Fix: The documentation for GitLab bootstrapping should explain exactly which permissions a fine-grained PAT needs in order to be used for bootstrapping Flux.
Based on my own experience, I believe the minimum permissions are:
If somebody can confirm that all of the above are necessary, and that no further permissions are necessary for other Flux features that I happen to not be using, I'll go ahead and write up a PR.
Fine-grained permissions documentation may also be missing for bootstrapping on other platforms (Bitbucket, Azure, GCS, Oracle, etc.) but I'll leave any issue-creation for those platforms to whatever communities use them.