Make positional parameters as a destionation paramater for auto-generated commands
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### Description
**What**
We need to make adjustments in this file.
https://github.com/apache/airflow/blob/a4f3417bb0ae22a447b974e5e543af45e55e3c7f/airflow-ctl/src/airflowctl/ctl/cli_config.py#L499-L584
airflowctl will understand whether the parameter is nullable. If it is not nullable, we should add as a destination parameter, and if it is nullable, it will be positional.
Example:
from
`airflow connections create --connection-id="test" --conn-type="test" ...`
to
`airflow connections create test test ...`
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
Contributor guide
Research direction
Start in airflow-ctl/src/airflowctl/ctl/cli_config.py at lines 499-584 and inspect how auto-generated command parameters are created. Determine how nullable and non-nullable parameters are identified, then verify that non-nullable values use destination parameters while nullable values remain positional, using the connections create examples as the expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 57/100