Allow service accounts to sign commits
Proposal
Tools such as renovatebot can be used to fully automate updates to package dependencies and keep tools up-to-date. Service accounts are a good fit for this use-case so that an extra license seat does not need to be used. Service accounts are currently unable to push commits on instances where signed commits are enforced. Service accounts performing extra git operations, such as commits, should be able to sign their own commits.
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17265 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17265 (closed)
- Developer
@hsutor I'm changing this to groupauthentication as it's about Service Accounts functionality.
1 - Viktor Nagy (GitLab) added groupauthentication label and removed groupenvironments label
added groupauthentication label and removed groupenvironments label
- Hannah Sutor added to epic &6777
added to epic &6777
- Hannah Sutor removed GitLab Free label
removed GitLab Free label
- Hannah Sutor changed milestone to %Backlog
changed milestone to %Backlog
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17341 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17341 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17440 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17440 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17607 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17607 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17709 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17709 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17794 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17794 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17900 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17900 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18065 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18065 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18164 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18164 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18246 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18246 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18353 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18353 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18437 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18437 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18633 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18633 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18718 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18718 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18802 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18802 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#18913 (closed)
mentioned in issue gitlab-org/quality/triage-reports#18913 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19083 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19083 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19194 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19194 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19283 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19283 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19367 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19367 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19538 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19538 (closed)
- Developer
The following customer is interested in this capability
- Subscription: GitLab Ultimate
- Product: self-managed
- Link to request: https://gitlab.zendesk.com/agent/tickets/580827
- Priority: customer priority7
- Crucial for projects, which have the requirement to enforce signed AND want use service accounts to push commits
- Why interested:
- We have projects, which have the requirement to enforce signed commits, but these projects are currently unable to use renovate (and similar bots)
- Problem they are trying to solve:
- Service accounts are currently unable to push signed commits
- Current solution for this problem:
- Do not use service accounts for a use-case, where service accounts are the best option
- Impact to the customer of not having this:
- We are unable to use service accounts for specific projects, where signed commits are required
- Questions:
- PM to mention: @hsutor
Collapse replies - Developer
Thank you @pmurray7 - we will continue to evaluate demand for this as we further build out service accounts functionality next year.
1
- 🤖 GitLab Bot 🤖 added customer label
added customer label
- Hannah Sutor removed sectioncd label
removed sectioncd label
- Hannah Sutor removed devopsdeploy label
removed devopsdeploy label
- 🤖 GitLab Bot 🤖 added sectionsec label
added sectionsec label
- 🤖 GitLab Bot 🤖 added devopssoftware supply chain security label
added devopssoftware supply chain security label
- 🤖 GitLab Bot 🤖 added Category:System Access label
added Category:System Access label