-
Notifications
You must be signed in to change notification settings - Fork 24
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
refactor: move iam-specific functionality to a shared class #150
Conversation
This will allow other authenticators that interact with the IAM service to share configuration and functionality.
@@ -119,294 +141,5 @@ describe('iam_token_manager_v1', () => { | |||
const token = await instance.getToken(); | |||
expect(token).toBe(ACCESS_TOKEN); | |||
expect(requestMock).not.toHaveBeenCalled(); | |||
done(); | |||
}); | |||
|
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.
All of these tests below were consolidated and are covered by the tests for the new IAM request based token manager
expect(logger.verbose.enabled).toBeFalsy(); | ||
expect(logger.info.enabled).toBeFalsy(); | ||
expect(logger.error.enabled).toBeFalsy(); | ||
expect(logger.debug.enabled).toBeFalsy(); |
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.
These were failing locally. Honestly, I'm not sure how they were ever passing. We never set those fields to false
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.
LGTM
🎉 This PR is included in version 2.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This will allow other token managers that interact with the IAM service to share configuration and functionality. This change is being made in advance of a new container-based token manager being added that will utilize this shared functionality, as it will interact with the IAM service as well.
cc @pyrooka