Repository navigation
feat(api): expose effective queue in task action metadata - #8245
Merged
Merged
Conversation
Signed-off-by: Carina Ursu <carina@union.ai>
kumare3
reviewed
Oct 27, 2026
| // Effective target queue for this task action, including the run default when | ||
| // no action-level queue override was specified. Unset when the queue is unknown | ||
| // or the action type does not use a task queue. | ||
| optional string queue = 19; |
Contributor
There was a problem hiding this comment.
we dont need it. It is already in TaskAction Metadata and that is the one to use.
Signed-off-by: Carina Ursu <carina@union.ai>
ursucarina
changed the title
ursucarina
enabled auto-merge (squash)
October 27, 2026 00:26
kumare3
approved these changes
Oct 27, 2026
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
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.
Why are the changes needed?
Task actions can override the run's default queue, but the public action read model does not expose their queue. Clients cannot reliably display an action's effective target queue from the run default alone.
What changes were proposed in this pull request?
Add optional
TaskActionMetadata.queue(field 4), exposed asmetadata.task.queuein action details and list/watch JSON responses. Its contract is the effective task queue, including the recorded run default when no action override was set; it is absent when the effective queue is unknown. Queue metadata is scoped to task actions through the existing metadata oneof. Regenerate Go, Python, Rust, and TypeScript bindings.This branch starts from the Flyte main commit currently pinned by the downstream consumer, keeping the dependency change limited to this additive field.
How was this patch tested?
go test ./gen/go/flyteidl2/workflow(generated package compilation).TaskActionMetadata, with no queue field onActionMetadata.git diff --check.Check all the applicable boxes