-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
physical/gcs: use separate client for updating locks #9424
Conversation
|
||
// Client | ||
opts := []option.ClientOption{option.WithUserAgent(useragent.String())} | ||
if credentialsFile := c["credentials_file"]; credentialsFile != "" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has been deprecated for a very, very long time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kalafut this might be fine to remove since we've had this notice for ~2yrs, but we should call this out in the changelog.
Tests:
|
|
||
// Client | ||
opts := []option.ClientOption{option.WithUserAgent(useragent.String())} | ||
if credentialsFile := c["credentials_file"]; credentialsFile != "" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kalafut this might be fine to remove since we've had this notice for ~2yrs, but we should call this out in the changelog.
@calvn updated - PTAL. |
* physical/gcs: use separate client for updating locks * Address review comments Co-authored-by: Calvin Leung Huang <[email protected]>
* physical/gcs: use separate client for updating locks * Address review comments Co-authored-by: Calvin Leung Huang <[email protected]> Co-authored-by: Seth Vargo <[email protected]>
* physical/gcs: use separate client for updating locks * Address review comments Co-authored-by: Calvin Leung Huang <[email protected]>
Same rationale and design as #9423.