Make required params positional for auto-generated airflowctl commands

[shivaam]

Required non-boolean parameters in auto-generated CLI commands are now positional instead of flag-style, improving UX consistency with manually defined commands like dags pause.

Before:

airflowctl connections create --connection-id="test" --conn-type="mysql" --password=secret
airflowctl dags get --dag-id=example_bash_operator

After:

airflowctl connections create test mysql --password=secret
airflowctl dags get example_bash_operator

Changes

• Track which operation parameters have default values during AST parsing
• For primitive params, use the default info to decide positional vs flag
• For Pydantic model fields, use is_required() to decide positional vs flag
• Use _UNSET for arg_dest default to avoid argparse crash on positional args
• Skip the has_default metadata key at runtime when mapping CLI args to method params
• Updated unit tests and integration test commands to match new positional syntax
• Added 2 new tests for positional arg behavior and default detection
• Added newsfragment for the breaking change

Notes

• _create_arg stays a dumb pass-through builder — all positional/flag logic is in the callers via one-liner conditionals
• Booleans are never positional (they need --flag/--no-flag)
• No special-casing for specific operations
• Breaking change: existing --flag=value syntax for required params will no longer work. Since airflowctl is new and not yet stable, this should be acceptable.

Open question

Posted a clarifying question on the issue about whether all required params should be positional (e.g., xcom add has 5 positional args), or if we should limit it.

closes: #60142

---

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

• Yes — Claude Code (Claude Opus 4.6)

Generated-by: Claude Code (Claude Opus 4.6) following the guidelines

[bugraoz93]

Thanks for the PR! I addressed your question. Could you please amend it to be both optional and positional, live side by side?
This way, we won't break anything while working, but rather add Airflow CLI positional arguments to improve parity and make migrations easier.

[bugraoz93]

This news fragment is for Airflow Core and not related to anything within airflowctl flow.
Since we are still in 0.x, significant changes are also expected at a certain level.
We are logging these things in the release notes

https://airflow.apache.org/docs/apache-airflow-ctl/stable/release_notes.html#significant-changes