potiuk commented on PR #45300:
URL: https://github.com/apache/airflow/pull/45300#issuecomment-2726804704
> Thanks Jarek! How about I remove the connection command integration from
the PR? Let's merge the API integration without integrating into any command so
that maintaining that part would be a lot easier even while moving out of the
package. I then make the split into `apache-airflow-cli` and add this
connection integration there. From there we start the transition to other
remote commands.
Yeah. I think we could separate it out to a separate change - and do
everything so that it works "locally" without authenticaion - but refactoring
to make it possible "separately" is good now.
> For the having all in the `apache-airflow-core` too is indeed tricky. We
should come up with something that shouldn't need duplicate work for API and DB
calls separately for each command if we don't want to remove remote commands
from `apache-airflow-core`.
Yeaah. Once I finish the `apache-airflow-core` we can add
`apache-airflow-cli` and figure out how to avoid or mitigate duplicaiton.
My first thought (also got a quick chat with @jedcunningham0 is that some
duplication is OK as long as we have a pre-commit that will take care to
synchronize the client side in `apache-airflow-cli` with the command and
"server" side in the API/scheduler. Does it sound good?
BTW. I just reserved `apache-airflow-cli` and `apache-airflow-ctl` in `PyPI`
for that separate distribution.
--
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]
