Go SDK: Refresh Go SDK execution API tokens#70168
Open
viiccwen wants to merge 1 commit into
Open
Conversation
Go Edge Worker tasks begin with workload-scoped credentials, while subsequent task API calls require execution scope. Without adopting server reissues, heartbeats and final state reports fail with 403. Signed-off-by: viiccwen <vicwen@apache.org>
Contributor
Author
|
cc @jason810496, @henry3260. 🙌 |
viiccwen
changed the title
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
1 participant
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.
Go Edge Worker tasks start with a workload-scoped token that is only authorized to call the task
/runendpoint. That response provides an execution-scoped token in theRefreshed-API-Tokenheader, but the Go Execution API client continued using the original workload token. As a result, heartbeats, runtime API calls, and final-state reporting failed with403 Forbiddenafter the task started.Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.