-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Removing support for API_KEY auth in translate. #2823
Conversation
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.
Yay!
Removing support for API_KEY auth in translate.
Hey folks -- what was the reason why we did this? I went down the rabbit hole and I can see that everyone agreed it was a good idea, but nowhere can I find an explanation as to why. Cards on table: I had a "bug" filed on this recently (internal folks: b/64123162), and so I need to grok what the appropriate answer is (e.g. whether to put this support back, or say that we are not going to do it because ______). |
@lukesneeringer, as I recall, it was mostly because the API key auth was outside of the normal authentication methods and I believe it was said that API key based auth was going away..or they(backend) were trying to not support it in the future. |
@lukesneeringer the description @daspecster gave matches my memory. Sort of an extension of "Special cases aren't special enough to break the rules." |
API keys are strongly being discouraged for Cloud APIs, especially for client libraries targeting backend languages. Omar has more details. :) |
Thanks. :-) |
Removing support for API_KEY auth in translate.
Fixes #2734.
/cc @jonparrott @jgeewax