enforce that user access token is used when committing from harness to git
in progress
M
Mint Locust
We would like to store pipeline.yaml in an external git in order to have a clear history of changes that are made to these configurations. By default, commits are made back to git using the service user credential defined in a git connector, but our company's engineering standards require all commits in our git instance are done by a real person, not a service user. The "Providers" functionality allows harness to commit as an individual, but there is no way to force that a user has a provider access token configured. We would like a way to enforce that pipelines cannot be saved in harness unless that save will be done using an end user's access token.
Log In
This post was marked as
in progress
Prasad Satam
under review
Mint Locust - Thanks for the feedback, we will take a look at this again and see if we can have a setting or some form of governance to enforce the use of OAuth /user creds.
Prasad Satam
complete
Mint Locust- Thanks for the feature request! We have a way to address this use case by integration with OAuth - https://developer.harness.io/docs/platform/git-experience/oauth-integration/
M
Mint Locust
Prasad Satam that feature allows users to make commits as themselves, but doesn't force them to. If a user does not have a bitbucket access token it will still use the service user credentials stored in the connector. We want to enforce that commits cannot happen unless they are being done by a logged in user.