Deployment Authorization / Code Committer Check
in progress
D
Detailed Camel
As a platform operator I want to ensure developers cannot authorize deployments of code they committed.
This is related to when pipeline is launched via the trigger.
When launched via the trigger, we need to determine who the committer is and that person cannot be DA approver. When implementing this, the email/ SID of the committer needs to be captured along with the commit ID. When there is a merge commit, then we need to capture the PR approver SID too. The PR approver SID should be allowed to perform the DA function
Log In
This post was marked as
in progress
D
Detailed Camel
Thank you! The duplicates were filed in error.
Rohan Gupta
Rubber Scallop This is the request to track, the team had filed 3 other duplicates, I have sperated them and rejected them. This will be the source of truth for your team.
R
Rubber Scallop
Rohan Gupta Will circle back with you. I informed the dev and he needs to do some research. My goal is to have a response by tomorrow, 4 Dec.
T
Tangerine Crocodile
Rubber Scallop Rohan Gupta We are using an on-perm Bitbucket server, and its not possible to associate a Bitbucket user with a Harness user
R
Rubber Scallop
Rohan Gupta Sharing what happens when we try the recommendation as we aren't using BB Cloud, but we are using our on-prem server version.
Rohan Gupta
long-term
Rohan Gupta
rejected
No response in 2 months closing the request, please respond to open it back up or file a new request.
Rohan Gupta
pending feedback
Has the team associated their Git User with their Harness user? The reason I ask is because currently we do not have a mapping between the Harness user and Third party git provider like Bitbucket, or Gitlab user today, but one way to address it is to associate a git user with the Harness user.