Description
What's happening?
When attempting to create a CBBS GCP repository through the CLI using --cloud-credentials-id and --cloud-credentials-key, GCP auth fails with:
'credentials are not valid: refresh_token is required'
|
There is no option to pass in this refresh_token, making static creds unusable here
What's expected?
I expect there to be an option to pass in the refresh_token
Steps to reproduce
- Set up a node with backup service
- Attempt to add a GCP CBBS repo through the CLI e.g.
-
/opt/couchbase/bin/couchbase-cli backup-service -c 10.112.212.101:8091 -u Administrator -p password repository --add --id new-repository --backup-archive gs://testrunner-gcp-jmj-test/test-arcihve --plan _daily_backups --cloud-staging-dir /tmp/test-staging --cloud-credentials-id REDACTED --cloud-credentials-key REDACTED
- Should see the following error:
-
ERROR: {'status': 400, 'msg': 'credentials are not valid: refresh_token is required'}
Attachments
For Gerrit Dashboard: MB-51280 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
171685,3 | MB-51280 Add support for supplying GCP credentials refresh token | neo | couchbase-cli | Status: MERGED | +2 | +1 |
171691,1 | Merge branch 'neo' into master | master | couchbase-cli | Status: MERGED | +2 | +1 |