-
Notifications
You must be signed in to change notification settings - Fork 1.7k
GitHub app access token lookup: allow to use PyJWT + cryptography instead of jwt #10664
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
base: main
Are you sure you want to change the base?
GitHub app access token lookup: allow to use PyJWT + cryptography instead of jwt #10664
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
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.
Thanks for your contribution!
Co-authored-by: Felix Fontein <felix@fontein.de>
Co-authored-by: Felix Fontein <felix@fontein.de>
Co-authored-by: Felix Fontein <felix@fontein.de>
Co-authored-by: Felix Fontein <felix@fontein.de>
Co-authored-by: Felix Fontein <felix@fontein.de>
If I may suggest, give it a try to https://pypi.org/project/andebox/ You can run this sanity test easily in your local machine by simply running:
|
Though I suspect I am coming too late with that information :) |
I have a way to run it via |
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
SUMMARY
Change community.general.github_app_access_token lookup to use PyJWT (https://pypi.org/project/PyJWT/) rather than jwt (https://github.com/GehirnInc/python-jwt).
Fixes #10299
this is a continuation of #10332
ISSUE TYPE
COMPONENT NAME
github_app_access_token
ADDITIONAL INFORMATION
Change the implementation to use pyjwt, rather than jwt that causes conflits elsewhere in the Ansible ecosystem.
thank you @blavoie for the intial commit and fixes. This pr would include both the compatibility issue and (hopefully) the required test cases
Im not too sure about how deprecation warning are usually shown in this collection, I've make used of
display.deprecated
function with a magic version number, any direction on this would be appreciated