feat(lab5): durable async attachment pipeline through grade 4

- RabbitMQ quorum queue, persistent messages and publisher confirms
- S3 staging plus PostgreSQL attachments/jobs outbox transaction
- worker variants (thumbnail, crop, optimized WebP), DB lease and lease sweeper
- jittered retry, permanent failures, explicit replay and admission cap
- deterministic crash hooks, resilience script and evidence for grade 4
- async-aware custom tests, oversized pixel case, docs and changelog
This commit is contained in:
Mikhail Verkovykh
2026-11-15 00:30:36 +03:00
parent 28d68dc30b
commit 9e43faa536
48 changed files with 4077 additions and 333 deletions
+2 -1
View File
@@ -19,7 +19,8 @@
"s3:DeleteObject"
],
"Resource": [
"arn:aws:s3:::__BUCKET__/attachments/*"
"arn:aws:s3:::__BUCKET__/attachments/*",
"arn:aws:s3:::__BUCKET__/staging/*"
]
}
]
+9
View File
@@ -13,6 +13,15 @@ set -eu
: "${S3_APP_POLICY:?S3_APP_POLICY is required}"
: "${S3_POLICY_TEMPLATE:?S3_POLICY_TEMPLATE is required}"
# AGENT: RustFS uses the user name as the access key, so the scoped identity
# the API signs with (S3_ACCESS_KEY_ID) must be the same string as S3_APP_USER.
# Divergence used to bootstrap successfully but every API readiness probe then
# saw 403 Forbidden, which is much harder to diagnose than a failed startup.
if [ "$S3_APP_USER" != "$S3_ACCESS_KEY_ID" ]; then
echo "S3_APP_USER ($S3_APP_USER) must equal S3_ACCESS_KEY_ID ($S3_ACCESS_KEY_ID): RustFS uses the user name as the access key" >&2
exit 1
fi
# AGENT: rc stores its alias file in $HOME. The image runs as an unprivileged
# user, so point HOME at a writable temporary directory.
export HOME="${HOME:-/tmp}"