Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea: create a specialized CI user #3

Open
akhmerov opened this issue Jul 29, 2018 · 0 comments
Open

Idea: create a specialized CI user #3

akhmerov opened this issue Jul 29, 2018 · 0 comments

Comments

@akhmerov
Copy link

Gitlab CI does not allow to push via token, which may be useful for multiple purposes. The feature request is now open for 2 years, and still requires a design decision on the gitlab side AFAIK.

A possible workaround is to make access credentials available to CI. This can be done in multiple ways, but I think the easiest is to use http access via a token.

If a regular user wants to set up CI in this way, we're limited to store the user's API token in the repository variables. This comes with the risk of exposing all the user's access to gitlab.

On the other hand, an admin has a much better option: they may create a dedicated user, mark it as external (to limit the scope of what that user can do), mark the user's account as private, add the user to the repository as developer, and add the bot user impersonation token to the repository variables.

Then if the users wanted to give that bot access to another repository (e.g. a dependency), they may give the bot the corresponding permissions.

Further, this could be used in combination with gitlab's system hooks for repository creation and deletion to make creation of such bot users automatic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant