Description
Description
There should be a way for Admins and Developers to create a service account or an "organisation access token" which is not directly related to a single user.
As a workaround, we can create a user specifically for such use cases. eg: "engineering@example.com"
Tech notes:
At the moment our backend assumes there is always a user behind all the API calls / actions. We would have to shift away from this. This is something that could also help with "embedding" where the assets are served without an anonymous user that is not part of the organisation.
Service accounts should have scopes. eg: scope to manage service accounts, manage projects, etc
What problem does this solve?
So we don't associate the CI/CD token to a personal account.
When a user/admin leaves the org it doesn't break the CI/CD pipelines.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status