I'm trying to run the Runner with the BITBUCKET_ACCESS_TOKEN variable as described in option 3, like in kustomize:
But I am getting the following error:
✖ At least one authorization method of (BITBUCKET_USERNAME, BITBUCKET_APP_PASSWORD) or (BITBUCKET_OAUTH_CLIENT_ID, BITBUCKET_OAUTH_CLIENT_SECRET) required.
I saw that this option is allowed for use in version 3.5 code but the validator does not allow using this option.
Does anyone know if there is any way to get past this or if this is on the Roadmap?
Hello @Erick Dzadotz ,
thank you for reaching out to Community!
The autoscaler tool only currently supports basic authentication (username and app password) and OAuth (client Id and Secret). This is described more in detail in the Authorization section of the runners-auto-scaler README file.
I understand it would be great to also support access tokens for the authentication, so I went ahead and raised a feature request with your development team :
Feel free to add your Vote there, as it helps our product managers to understand the demand for the feature. You can also set yourself as a watcher so you will be notified whenever there's any update on that feature.
Thank you, @Erick Dzadotz !
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.