enable using a Repository Access Token instead of a Service Account
I would like to be able to use a repository access token instead of a service account to connect to VC (Bitbucket in my case). https://support.atlassian.com/bitbucket-cloud/docs/repository-access-tokens/
The main benefit for me would be the ability to conveniently authenticate while maintaining a high level of security, even in situations where corporate change management policies and SSO requirements can be cumbersome.
Jonathan Flatt
shared this idea
-
tbugbee@aflac.com
commented
Agree with this! Access tokens are an industry standard for integration requirements, and rate limiting really shouldn't be a factor for a CI/CD tool.
-
This would allow us to take advantage of Bitbucket's rate limit increases: https://support.atlassian.com/bitbucket-cloud/docs/api-request-limits/ which are only available by using a "workspace, project, repository access tokens for authentication or make requests through programmatic access via a Forge app."
I believe this would alleviate a major pain point we've been experiencing due to being rate limited by bitbucket. These rate limits are hindering our ability to scale up our CI/CD pipeline.