Repository navigation
Add scoped Execution API access for Dag processors - #74370
Merged
ephraimbuddy merged 6 commits intoOct 14, 2026
Merged
Conversation
boring-cyborg
Bot
added
area:API
1 task done
ephraimbuddy
marked this pull request as ready for review
October 7, 2026 12:20
ephraimbuddy
requested review from
XD-DENG,
amoghrajesh,
ashb,
bugraoz93,
choo121600,
dheerajturaga,
henry3260,
jason810496,
jedcunningham,
jscheffl,
kaxil,
potiuk and
shahar1
as code owners
October 7, 2026 12:20
ashb
reviewed
Oct 7, 2026
ashb
reviewed
Oct 7, 2026
ashb
left a comment
ashb
left a comment
Member
There was a problem hiding this comment.
(Only skimmed first 25% of PR so far)
kaxil
approved these changes
Oct 8, 2026
ephraimbuddy
force-pushed
the
dag-processor-api-foundation
branch
from
October 9, 2026 08:40
f2b0be1 to
eb40af7
Compare
Contributor
Author
|
Please don't merge until main is 3.5.0 |
ashb
changed the title
ephraimbuddy
force-pushed
the
dag-processor-api-foundation
branch
from
October 12, 2026 13:41
7f41241 to
3a7e258
Compare
ephraimbuddy
changed the title
Dag processors need credentials tied to their registered Job and granted bundles before they can communicate with a remote Execution API. Keep this foundation independently reviewable while the processor command retains its existing database-backed behavior.
The heading warning prevents the security documentation from building successfully.
New Dags can query execution state while parsing, before they have a DagModel row. Rejecting those requests prevents their initial parse from completing.
Task and processor credentials need distinct validation so task-only routes cannot receive processor identities. Expired provisioning credentials must not leave a registered Job behind, while trusted in-process task identities must remain usable without JWT expiry.
Provisioner restarts and transient write failures must not interrupt running processors. Failed registration must not leave an incomplete Job that a retry can adopt.
Slow CI responses can exceed the best-effort renewal deadline, while the authentication guidance must reflect the scoped Execution API contract.
ephraimbuddy
force-pushed
the
dag-processor-api-foundation
branch
from
October 14, 2026 06:42
3a7e258 to
c0699b3
Compare
1 task done
1 task done
1 task done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Give Dag processors scoped access to the Execution API without giving them the API signing key. Trusted provisioning issues a bundle-scoped session token, registration exchanges it for a Job credential, and the processor exchanges that credential for individual parsing-attempt tokens.
This PR provides Job registration, heartbeat and completion, credential renewal, bundle/team authorization, and the processor-side HTTP client. It also adds the Job identity migration and versioned API contracts.
This is the foundation for #74233, which adds the processor integration, result publication and deployment support. The normal
airflow dag-processorcommand keeps its existing behavior in this PR.Was generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-6) following the guidelines