Allow to take arguments

[xixixao]

Migrations are helpful once there is thousands of documents in any table. For a job like "delete all documents before date x", it's nice to be able to configure this when running the migration, instead of hardcoding x into the migration code.

Should be trivial to implement, and validators could be used to check the argument shape.

[ianmacartney]

Care to put up the PR? I think there's two separate types of args here: ones that parametrize a `customRange`, and ones where the args are available in the migration itself. Currently both could maybe use an environment variable? But that isn't encoded into the run.

…

On Wed, Mar 11, 2026 at 7:04 AM Michal Srb ***@***.***> wrote: *xixixao* created an issue (get-convex/migrations#30) <#30> Migrations are helpful once there is thousands of documents in any table. For a job like "delete all documents before date x", it's nice to be able to configure this when running the migration, instead of hardcoding x into the migration code. Should be trivial to implement, and validators could be used to check the argument shape. — Reply to this email directly, view it on GitHub <#30>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACZQW2JVL25NCF2F27QMWT4QFW5VAVCNFSM6AAAAACWOKV6QSVHI2DSMVQWIX3LMV43ASLTON2WKOZUGA2TQNBTGMZTSOA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ianmacartney]

Whoops just saw the PR - overall I think it is useful. Maybe a "backfill/livefill" component is more idiomatic, but not the worst thing to have this be more capable. Let me know how the pkg-pr-new package works out

[xixixao]

pkg-pr-new very cool! I've been testing it via my own publish. I do think it has some rough edges (like args to runner with a list argument is not typechecked and has to be the same for all migrations - but fine for our use case).