>> well as internal API you need a web endpoint incl. minimal
> > > authentication.
> > > >> Some base admin tooling is needed for bootstrap and base admin. Like
> > > >> creating the first admin user is impossible if no user.
> > > >>
> >
On 2024/02/19 10:34:44 Bolke de Bruin wrote:
> with regards to the api client: the intention was indeed to remove direct
> access to the DB, which I think is still a valid thing to do. In my
opinion
> the underlying question is what are we going to do with direct DB access
> from the cli. Is that
ropose to document details and
> make
> > >> an AIP to discuss, that might be easier then a reply-to-all thred to
> > define
> > >> the scope of cleanup. Also and especially for API cöient we need to
> > check
> > >> for impact if breaking changes app
ne
> >> the scope of cleanup. Also and especially for API cöient we need to
> check
> >> for impact if breaking changes appear.
> >>
> >> Jens
> >>
> >> Sent from Outlook for iOS<https://aka.ms/o0ukef>
> >>
>
impact if breaking changes appear.
>>
>> Jens
>>
>> Sent from Outlook for iOS<https://aka.ms/o0ukef>
>> ____
>> From: Andrey Anshin
>> Sent: Monday, February 19, 2024 3:54 PM
>> To: dev@airflow.apache.org
t: Monday, February 19, 2024 3:54 PM
> To: dev@airflow.apache.org
> Subject: Re: [DISCUSS] Deprecate cli options in Airflow Configurations and
> airflow.api.client
>
> >Actually - it's not at all part of AIP-44 :). Airflow CLI was
> (consciously and deliberately) not part of it.
cöient we need to check for impact if
breaking changes appear.
Jens
Sent from Outlook for iOS<https://aka.ms/o0ukef>
From: Andrey Anshin
Sent: Monday, February 19, 2024 3:54 PM
To: dev@airflow.apache.org
Subject: Re: [DISCUSS] Deprecate cli options in A
>Actually - it's not at all part of AIP-44 :). Airflow CLI was
(consciously and deliberately) not part of it.
Then better to check whether or not it accidentally uses it, add to my
checklist
> So I would be very much for removing that whole part - even in Airflow
2.9.
+1 for removal if it
Actually - it's not at all part of AIP-44 :). Airflow CLI was (consciously
and deliberately) not part of it.
CLI is specifically treated as a "local" tool that is executed inside the
security perimeter where direct database access is needed (i.e. it falls in
the same category as 'scheduler',
> the underlying question is what are we going to do with direct DB access
from the cli
Good point!
I guess it should be covered by AIP-44, so if there are no methods which
implement these actions by AIP-44 it is better to create it instead of just
moving old code.
On Mon, 19 Feb 2024 at
with regards to the api client: the intention was indeed to remove direct
access to the DB, which I think is still a valid thing to do. In my opinion
the underlying question is what are we going to do with direct DB access
from the cli. Is that something we want to keep or do we want a different
Greetings guys!
I want to start a discussion about deprecation cli configuration options
https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#cli
as well as `airflow/api/client` in upcoming minor/feature release of
Airflow (2.9 or 2.10 depends on).
This options control
12 matches
Mail list logo
