I've checked the discussions and issues section of github (or slack) but 
couldn't find anywhere the topic which provider is being moved by whom?

Maybe I'm looking at the wrong place or looked over it...

-----Original Message-----
From: Kunal Bhattacharya <[email protected]> 
Sent: Thursday, 30 January 2025 15:09
To: [email protected]
Subject: Re: [ANNOUNCEMENT] Moving Providers to separate sub-projects soon-ish

[You don't often get email from [email protected]. Learn why this is 
important at https://aka.ms/LearnAboutSenderIdentification ]

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 [email protected]<mailto:[email protected]>.

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, <[email protected]> wrote:

> FYI: I've started a new PR to move the Microsoft related providers to 
> the new folder structure
>
> -----Original Message-----
> From: Jarek Potiuk <[email protected]>
> Sent: Sunday, 26 January 2025 12:47
> To: [email protected]
> 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 [email protected]<mailto:
> [email protected]>.
>
> 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.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to