jedcunningham commented on PR #45300:
URL: https://github.com/apache/airflow/pull/45300#issuecomment-2726706326

   So, after sleeping on this idea, I want to pitch it...
   
   Have you considered having this new api-driven cli be completely standalone 
and in its own package from day 1? This would leave the existing db-backed cli 
as-is and functional. The vast majority of this PR is still usable, it'd just 
not be in `airflow` and not whack the old command.
   
   I'm imagining the scenario where I'm trying to troubleshoot in a remote 
deployment, jump into the scheduler pod, and try to run `airflow config 
get-value x y`. Having to auth not on my machine, where other people could also 
have access and grab my token, then clean up when I'm done isn't ideal. 
Effectively it'd have to do my troubleshooting remotely, which could be bit a 
bit cumbersome.
   
   Basically, this new api-driven command could be more like kubectl, 
airflowctl.


-- 
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]

Reply via email to