Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Switch signUrl method in google-cloud-storage to use v4 as default signature version #41

Open
houglum opened this issue Sep 26, 2019 · 2 comments
Open

Switch signUrl method in google-cloud-storage to use v4 as default signature version #41

houglum opened this issue Sep 26, 2019 · 2 comments
Labels
api: storage Issues related to the googleapis/java-storage API. type: process A process-related concern. May include testing, release, or the like.

Comments

@houglum
Copy link
Contributor

houglum commented Sep 26, 2019

V2 is discouraged in favor of V4. We should figure out a way to migrate users to use V4, and at some point in the future (TBD), we should make the default signature version V4 instead of V2.
@frankyn
Copy link
Member

frankyn commented Sep 27, 2019 •
edited
Loading

A migration plan is defined internally but pending v4 being default timeline.

@houglum
Copy link
Contributor Author

houglum commented Sep 27, 2019 •
edited by frankyn
Loading

I mostly made this issue so that code TODOs could reference it :)
~~ redacted migration plan link~~ (@frankyn)

@chingor13 chingor13 transferred this issue from googleapis/google-cloud-java Jan 7, 2020
@chingor13 chingor13 added the type: process A process-related concern. May include testing, release, or the like. label Jan 7, 2020
@google-cloud-label-sync google-cloud-label-sync bot added the api: storage Issues related to the googleapis/java-storage API. label Jan 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api: storage Issues related to the googleapis/java-storage API. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chingor13 @frankyn @houglum