New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Followup S3 blob work #700

Closed

5 tasks done

ktuite opened this issue Sep 3, 2024 · 0 comments

Assignees

Member

ktuite commented Sep 3, 2024 •

edited

Loading

Followup to issue #585 after merging PR getodk/central-backend#1071

Must have:

To consider:

Move pgrowlocks requirement to tests s3: remove PGROWLOCKS extension from db-migrations central-backend#1190
logging events? upload succeed, upload failed etc.?
make an audit log event from nightly processing job
should migrating back from s3 to postgres be supported?
- "Once you opt into using S3-compatible storage, you can't opt back out of it and migrate files back to the database." (central-install: document s3 config docs#1859)

For after .2:

nginx config to mask URLs: s3: handle 307 redirects #716

Noting ideas/questions that came up but that we will park for now:

tests for missing blobs, e.g. a single missing blob in a data export?
are there race conditions in purge code? purge vs blobs re-attaching?

matthew-white mentioned this issue

Update user docs for Central v2024.2 getodk/docs#1786

Closed

3 tasks

ktuite closed this as completed

matthew-white assigned alxndrsn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment