Do not touch last_downloaded_at when on a geo secondary
🔥 Problem
In Add last_downloaded_at to packages (!97143 - merged), we added a last_downloaded_at
to the package model.
That field is bumped/touched when a package is pulled for downloaded. This field is not displayed yet but it will used in cleanup policies (see #371011).
The problem is that users could pull packages from geo secondaries but geo secondaries are read-only mirrors, so guess what happens when we try to bump a column in the packages table? Yes,
🚒 Solution
Fortunately, bumping the last_downloaded_at
field is centralized in a model function. So the solution is quite trivial:
- Add a guard to that function: if we are in a geo secondary, return early.