Make the Go SDK GCS client load the credentials internally on the first 401
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
From lcwik in https://github.com/apache/beam/pull/491:
"Is there any way to make the client load the credentials internally on the first 401?
It seems like we should only get the credentials if they are asked. We should still be able to pass in the scope that we want for the client."
Imported from Jira [BEAM-3896](https://issues.apache.org/jira/browse/BEAM-3896). Original Jira may contain additional context.
Reported by: herohde.
Contributor guide
Research direction
Start by reading the referenced Apache Beam pull request 491 and the imported Jira issue BEAM-3896 for the missing context, then locate the Go SDK GCS client. Confirm how the client receives its scope and handles a 401. Done means credentials are loaded internally only after the first 401 while the requested scope can still be passed to the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100