-
Notifications
You must be signed in to change notification settings - Fork 409
feat: support scopes on compute credentials #642
Conversation
Codecov Report
@@ Coverage Diff @@
## master #642 +/- ##
==========================================
+ Coverage 88.25% 88.31% +0.05%
==========================================
Files 18 18
Lines 783 787 +4
Branches 86 87 +1
==========================================
+ Hits 691 695 +4
Misses 80 80
Partials 12 12
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #642 +/- ##
=========================================
Coverage ? 88.31%
=========================================
Files ? 18
Lines ? 787
Branches ? 87
=========================================
Hits ? 695
Misses ? 80
Partials ? 12
Continue to review full report at Codecov.
|
470ea56 to
c21304a
Compare
c21304a to
8fd0056
Compare
|
@bcoe @alexander-fenster this is ready for a look :) |
bcoe
left a comment
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 seems good to me.
If I understand the code properly, does this mean that we need to set the same options when generating a refresh token as when we initially request an access token?
| property: tokenPath, | ||
| params: { | ||
| scopes: this.scopes | ||
| // TODO: clean up before submit, fix upstream type bug |
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.
is this still a TODO prior to landing?
The GCE metadata server is adding support for requesting tokens against user accounts with a predefined set of scopes. This adds experimental support for passing the scopes as querystring parameters to the metadata service in compute credentials.