kolaenteandTink fa9fc4e06f feat(migration): keep queued import uploads in the file storage ...

The upload was spooled to the receiving instance's temp dir and only its
name travelled with the event. That holds while events stay in-process,
but it ties the job to the instance that accepted the upload.

Store it through the files package on the configured backend and record
its id on the migration status, so the event carries only the status id
and any instance can run the import. The job copies it to a local temp
file first: the zip importer needs random access, which an S3 object body
cannot give.

The upload is removed once the import is over. An hourly cron deletes
leftovers from events lost on restart or instances that died mid-import.

2026-09-15 17:57:00 +02:00

..

common.go

…

events.go

feat(migration): keep queued import uploads in the file storage

2026-09-15 17:57:00 +02:00

handler_file.go

feat(migration): keep queued import uploads in the file storage

2026-09-15 17:57:00 +02:00

handler.go

feat(migration): record whether a migration succeeded

2026-09-15 16:59:37 +02:00

listeners_test.go

feat(migration): keep queued import uploads in the file storage

2026-09-15 17:57:00 +02:00

listeners.go

feat(migration): keep queued import uploads in the file storage

2026-09-15 17:57:00 +02:00

main_test.go

fix(migration): serialize imports per user

2026-08-31 18:37:03 +02:00

migration_handler_test.go

fix(migration): run file imports in the background

2026-09-15 16:59:37 +02:00

notifications.go

…