Closed ivanyu closed 1 year ago
Do we actually need all this machinery for checking if multiple ways to specify credentials were used simultaneously? Looks like a common approach is to specify the priority of credentials lookup and just use the first specified according to that priority, should we follow that?
I like the current approach better, it's intuitive for the user.
null
should be the default value forgcs.credentials.default
, because otherwise certain practical combinations are impossible (e.g. just settinggcs.credentials.json
without anything else).Also this commit refactors how the credentials settings are validated: the validation logic is completely delegated to
CredentialsBuilder
to have it in one place.