bugraoz93 commented on issue #57632:
URL: https://github.com/apache/airflow/issues/57632#issuecomment-3476439239
Thanks @Prab-27! I will take care of #57630 and #57629 to speed up the
release of initial versions. Thanks a lot for asking!
This one can be included in later releases, after discussion in the voting
attached to this issue, so I would be happy for you to take this one. My idea,
while writing this file-based approach, has a couple of advantages. Open to
different ideas for sure. The idea is to make it
* single source of truth
* easy to validate in the pre-commit using `get_parser()` from
`cli_parser.py`, where it gives the entire commands included into airflowctl
* easier integration into auto-generation since we are building the `parser`
and these are mainly impacting auto-generated ones, since we are writing
specific help text for those custom-built ones
So the YAML/JSON could look like, which should be only used for
auto-generated from the operation method implemented. This would mean auth
won't be included since it is a custom-created under `commands/`
```YAML
assets:
- create-event: "Creat an event for a given Asset ID"
- get: "Retrieve an asset for a given Asset ID"
- ....
backfill:
- create: "Create a backfill job for a given Dag ID and date range"
- get: "Retrieve backfill job details for a given backfill ID"
- list: "List all backfill jobs"
- ....
```
```JSON
{
"assets": {
"create-event": "Creates event for a given asset",
"get": "Retrieve an asset for a given asset-id",
"...": "..."
},
"backfill": {
"create": "Create a backfill job for a given Dag id and date range",
"get": "Retrieve backfill job details for a given backfill ID",
"list": "List all backfill jobs",
"...": "..."
}
}
```
Then we will add these instead of generating inside `CommandFactory`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
