Uh oh!
There was an error while loading. Please reload this page.
Add Support for GitHub App Installation Authentication in GithubHook - #54812
Conversation
Lee-W
left a comment
There was a problem hiding this comment.
hey sorry for late review. left a few comments. but I think we're close to merge
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
GithubHookLee-W
commented
Nov 19, 2025
still need some fix on CI failure. will take a look tomorrow |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
jason810496
left a comment
There was a problem hiding this comment.
Thanks for the update! Please feel free to resolve the addressed comments.
Sorry I should raise the nit in previous review:
How about adding unit test for get_conn method to check the new branch logic?
Thanks!
jeff3071
commented
Nov 21, 2025
Thanks for addressing this! |
Uh oh!
There was an error while loading. Please reload this page.
This PR adds support for GitHub App private keys stored directly in connections (e.g. in AWS Secrets Manager). `private_key` field is an alternative to `key_path`. This is a followup for apache#54812.
This PR adds support for GitHub App private keys stored directly in connections (e.g. in AWS Secrets Manager). `private_key` field is an alternative to `key_path`. This is a followup for apache#54812.
closes: #39457
Summary
This PR add support for GitHub App Installation Authentication in
GithubHook.If
access_tokenis not provided, readkey_path,app_id,installation_id, and optionaltoken_permissionsfrom extra field.Other Change
Related Document
Github app document
Example app installation authentication
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.