David, microsoft.azure provider move is already in progress. You can take up the others.
Thanks, Kunal Bhattacharya On Thu, 30 Jan 2025, 18:54 Blain David, <david.bl...@infrabel.be> wrote: > FYI: I've started a new PR to move the Microsoft related providers to the > new folder structure > > -----Original Message----- > From: Jarek Potiuk <ja...@potiuk.com> > Sent: Sunday, 26 January 2025 12:47 > To: dev@airflow.apache.org > Subject: Re: [ANNOUNCEMENT] Moving Providers to separate sub-projects > soon-ish > > EXTERNAL MAIL: Indien je de afzender van deze e-mail niet kent en deze > niet vertrouwt, klik niet op een link of open geen bijlages. Bij twijfel, > stuur deze e-mail als bijlage naar ab...@infrabel.be<mailto: > ab...@infrabel.be>. > > Ah: one small, important thing I forgot: For the new providers, NO LONGER > dependencies are maintained in `provider.yaml` - each new provider has it's > own `pyproject.toml` and you should edit all kinds of dependencies > (required, optional, devel) in the respective `pyproject.toml` of the > provider - so it became "absolutely standard" way of doing it for the new > providers. >
