Attempting to update deployment variables through API with a token fails.

[Brian_Daniels]

We are trying to update some tooling we have to set repo and deployment variables through the api to use API tokens instead of app passwords in light of their deprecation.

This works fine for repo variables, but when we try to set a deployment variable through the /deployments_config/environments/(env_uuid)/variables/ API call it returns a 403 error of 'This API is not accessible by this authentication mechanism'.

Calling the same endpoint with an app password works and updates the variable.  The token has a scope of read:pipeline:bitbucket and admin:pipeline:bitbucket.

How can we update these when authenticating using an API token?

[Aron Gombas _Midori_]

@Brian_Daniels I found an article in which the author works with the same end-point like you, and it seems he is also using the pipeline:variable scope. Maybe you need this, or there is a similar scope for environments, it might worth a research...

https://medium.com/@matiasquin/devops-wizardry-turning-bitbucket-variable-chaos-into-automation-bliss-18f392f89a70