-
Notifications
You must be signed in to change notification settings - Fork 471
fix: fixing anonymous access flag while creating client #4093
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4093 +/- ##
==========================================
+ Coverage 83.27% 83.35% +0.07%
==========================================
Files 153 153
Lines 18600 18602 +2
==========================================
+ Hits 15490 15505 +15
+ Misses 2539 2531 -8
+ Partials 571 566 -5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/gemini summary |
|
/gemini review |
|
Hi @vadlakondaswetha, @raj-prince, your feedback is needed to move this pull request forward. This automated reminder was triggered because there has been no activity for over 24 hours. Please provide your input when you have a moment. Thank you! |
* fixing anonmous flag fix * adding unit test
* fixing anonmous flag fix * adding unit test
* fixing anonmous flag fix * adding unit test
Description
Since 3.5.1,
enable-google-lib-authis set to true, which causes a cred.UniverseDomain query even for existing clients that set anonymous-access to disable authentication.Link to the issue in case of a bug fix.
b/465254339
Testing details
Any backward incompatible change? If so, please explain.