More this:
https://airflow.apache.org/docs/apache-airflow-providers/core-extensions/index.html
and
https://airflow.apache.org/docs/apache-airflow/stable/cli-and-env-variables-ref.html#executors

On Thu, Mar 13, 2025 at 5:29 PM Ephraim Anierobi <ephraimanier...@apache.org>
wrote:

> It looks like it's already added in the draft PR. Like in
> "provider_info.schema.json". Is that what you mean?
>
> On Thu, 13 Mar 2025 at 17:22, Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > Great idea. We might want to add it also to more "provider info" stuff
> > (does not have to be this PR - likely when we create 2nd or 3rd bundle).
> >
> > On Thu, Mar 13, 2025 at 5:14 PM Ephraim Anierobi <
> > ephraimanier...@apache.org>
> > wrote:
> >
> > > Hi everyone,
> > >
> > > I would like to propose moving the Git DAG bundle to a new Git
> provider.
> > >
> > > As part of AIP-66, we created a versioned Git DAG bundle(a new term) in
> > > the dag_processing package with a plan to eventually move it into its
> own
> > > provider package.
> > >
> > > Looking at the possibility of having other similar versioned bundles
> e.g
> > > S3 or Google Storage etc, I decided to create a new provider called git
> > and
> > > have the bundle live in the bundle's package inside the provider.
> Here’s
> > a
> > > draft PR of the proposed provider:
> > > https://github.com/apache/airflow/pull/47636
> > >
> > > I’m happy to hear what you think.
> > >
> > > Ephraim
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > > For additional commands, e-mail: dev-h...@airflow.apache.org
> > >
> > >
> >
>

Reply via email to