BTW. Big shoutout to Andrey who implemented the easy switch between the
clients, a few months ago (for ARM case) in the way that we could implement
the switch **really** quickly.  Kudos for anticipating the need :D

On Fri, Dec 15, 2023 at 4:45 PM Jarek Potiuk <ja...@potiuk.com> wrote:

> Hello everyone,
>
> This is a bit hurried, but the circumstances are unusual.
>
> Even if we use MySQL and not MariaDB as our "production ready" database
> we've lost a bit of faith in Oracle being a good steward of MySQL apt repos.
>
> More details can be found in:
> https://lists.apache.org/thread/dy3fgwhoc5m2f3tpqkwqcytrs6nhjlc4
>
> Oracle eventually replaced their keys with new ones after ~24 hours of
> breaking everyone who tried to install MySQL + breaking workflows of
> everyone who wanted to extend any of our images (which still need fixes as
> we only have workarounds for now) .
>
> I am calling for a consensus on:
>
> 1) switching our Intel/X86_64 to mariadb client (same as ARM images)
> 2) allowing the users to build their image to use mysql client
> 3) adding the new key but also removing mysql APT repository from the
> image to remove 2025 drama again
> 4) applying point 3) to all released images
>
> Anticipating (after the short discussion) that consensus will be reached,
> I am calling for it.
>
> We proceed with completing and merging
> https://github.com/apache/airflow/pull/36243 that implements points 1) 2)
> 3) (and later with point 4) by updating the images). Also Andrey improved
> our code to import the keys in
> https://github.com/apache/airflow/pull/36244. This will avoid some
> deprecation warnings and make our key-importing code more DRY.
>
> We will also release 2.8.0rc4 with these two cherry-picked shortly.
>
> No need to +1 this email, but if you think it's wrong, please respond with
> reasoning.
>
> J.
>
>
>

Reply via email to