Add worker-name filter to airflow edge list-workers

[shubhamraj-git]

In clusters with many edge workers, list-workers could only be narrowed by --state. This adds an optional --worker-name-pattern glob (e.g. 'prod-*', '*gpu*') that filters workers by name DB-side, composable with --state. This brings the CLI to parity with the edge UI/REST route, which already supports worker_name_pattern.

Usage:
airflow edge list-workers --worker-name-pattern 'bree-*'

Was generative AI tooling used to co-author this PR?

• Yes (Opus 4.8)

[dheerajturaga]

@shubhamraj-git, looks like there are conflicts. Can you resolve them?

What are your thoughts on extending the --edge-hostname to accept a pattern instead. Given we already have the argument we may be able to use the same variable rather than adding a new argument

[dheerajturaga]

Actually on second pass, the current approach is better. Could we rename this option from --name-pattern to --worker-name-pattern?

The command output and model field both use worker_name, and the edge API/UI already expose worker_name_pattern, so --worker-name-pattern makes the target field clearer. I'd avoid extending --edge-hostname for this, since that option is used as an exact worker identity for mutation commands.

---

Drafted-by: Codex (GPT-5); reviewed by @dheerajturaga before posting

[shubhamraj-git]

Actually on second pass, the current approach is better. Could we rename this option from --name-pattern to --worker-name-pattern?

The command output and model field both use worker_name, and the edge API/UI already expose worker_name_pattern, so --worker-name-pattern makes the target field clearer. I'd avoid extending --edge-hostname for this, since that option is used as an exact worker identity for mutation commands.

Drafted-by: Codex (GPT-5); reviewed by @dheerajturaga before posting

I gave it a thought before raising this PR,
but

airflow edge list-workers --worker-name-pattern PATTERN

sounds bit redundant on the worker side, so thought of going with just name-pattern since here name self explains it is for worker, let me know what do you think?

[dheerajturaga]

Actually on second pass, the current approach is better. Could we rename this option from --name-pattern to --worker-name-pattern?
The command output and model field both use worker_name, and the edge API/UI already expose worker_name_pattern, so --worker-name-pattern makes the target field clearer. I'd avoid extending --edge-hostname for this, since that option is used as an exact worker identity for mutation commands.
Drafted-by: Codex (GPT-5); reviewed by @dheerajturaga before posting

I gave it a thought before raising this PR, but

airflow edge list-workers --worker-name-pattern PATTERN

sounds bit redundant on the worker side, so thought of going with just name-pattern since here name self explains it is for worker, let me know what do you think?

just incase we want to use the same option for other edge CLIs it would make it clear

[dheerajturaga]

Awesome! Works as expected. Thanks for making adjustments as needed!