-
Notifications
You must be signed in to change notification settings - Fork 764
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
Fix: Support app auth and PAT via two provider instances #1538
Fix: Support app auth and PAT via two provider instances #1538
Conversation
This PR does not take into account your proposed alias keyword in #1537. Do you view this as a transitional step? Are you going to be updating this PR? |
Alright, I've spent a little more time looking into this. I can confirm the changes are as described:
The PR that introduced app auth, #753, mentions that the app_auth block "conflicts deliberately" with the token, but doesn't specify why. If this change unblocks others, I'm happy to ship it. |
@kfcampbell any progress? Looking forward to next gh provider release with a fix :) |
@kfcampbell Is there an update? Looking forward to seeing this in a new version |
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.
I'll get this merged now and released soon.
Co-authored-by: Nick Floyd <139819+nickfloyd@users.noreply.github.com> Co-authored-by: Keegan Campbell <me@kfcampbell.com>
Co-authored-by: Nick Floyd <139819+nickfloyd@users.noreply.github.com> Co-authored-by: Keegan Campbell <me@kfcampbell.com>
Resolves #1537
Behavior
Before the change?
The following code errors if both
GITHUB_APP_...
andGITHUB_TOKEN
env vars are set:The error message looks like this:
After the change?
app_auth {}
block set => Provider uses theGITHUB_APP_...
env vars (currently the case*), ignoresGITHUB_TOKEN
env var (new)app_auth {}
block not set => Provider uses theGITHUB_TOKEN
env var (currently the case*), ignoresGITHUB_APP_...
env vars (currently the case*)Other information
Additional info
Pull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!
Type: Breaking change
label)If
Yes
, what's the impact:Pull request type
Please add the corresponding label for change this PR introduces:
Type: Bug
Type: Feature
Type: Documentation
Type: Maintenance