Hi everyone,

I am happy to announce that the migration of connection UI metadata
from Python hook methods to declarative provider.yaml files is now
complete across all community-maintained providers.

Thank you to everyone who helped in this migration effort! I appreciate it.

Next steps:

- Deprecation warnings will be added to the Python fallback path to spread
the word about the new way of doing things.


Thanks & Regards,
Amogh Desai


On Tue, Feb 24, 2026 at 1:08 PM Amogh Desai <[email protected]> wrote:

> Amazing response from the community too, only 6 out of 28 providers are
> available for grabs!
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Mon, Feb 23, 2026 at 12:53 PM Jarek Potiuk <[email protected]> wrote:
>
>> Very cool :)
>>
>> On Mon, Feb 23, 2026 at 8:19 AM Amogh Desai <[email protected]>
>> wrote:
>> >
>> > Hello All,
>> >
>> > I have been working on decoupling connection form UI metadata from
>> runtime
>> > hook imports by moving it from python code into declarative
>> `provider.yaml`
>> > for providers, as discussed earlier in:
>> > https://lists.apache.org/thread/834jdpbzrb46zsm5ngtcvdm060yhfjfs
>> >
>> > I started this work in three phases which covered ~20 providers
>> including
>> > Google, Amazon, Azure, Kubernetes, Slack, SMTP, and others. We have
>> about
>> > ~30 remaining that will need the same treatment.
>> >
>> > Each provider can be considered to be a small, self-contained task -
>> which
>> > typically
>> > involves updating one `provider.yml` file and running a script to
>> generate
>> > the relevant
>> > data.
>> >
>> > Here's a tracking issue with step-by-step instructions on how to pick an
>> > provider
>> > and contribute to it: https://github.com/apache/airflow/issues/62345
>> >
>> > If you are looking for a good contribution opportunity, this is a great
>> > place to start too.
>> >
>> > Thanks & Regards,
>> > Amogh Desai
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>

Reply via email to