From b1a4f1afdadbffc2460f5d9ba52596230a005928 Mon Sep 17 00:00:00 2001 From: Lucas Vieira Date: Mon, 27 Apr 2026 22:13:38 -0300 Subject: [PATCH] test(rds): force postgres image rebuild for aws_s3 e2e The published `fakecloud-postgres:16-0.13.1` image lacks the aws_s3 extension files (they ship with the next release), so the runtime's pull-first path returned an image without the new extension and `CREATE EXTENSION aws_s3` failed in CI. Set `FAKECLOUD_REBUILD_POSTGRES_IMAGE=1` for this test so it always builds locally from the embedded assets in this commit. Goes away naturally once v0.13.2 publishes the image with aws_s3 baked in. --- crates/fakecloud-e2e/tests/rds_aws_s3.rs | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/crates/fakecloud-e2e/tests/rds_aws_s3.rs b/crates/fakecloud-e2e/tests/rds_aws_s3.rs index 8401ff92..8597177e 100644 --- a/crates/fakecloud-e2e/tests/rds_aws_s3.rs +++ b/crates/fakecloud-e2e/tests/rds_aws_s3.rs @@ -42,7 +42,12 @@ async fn connect_with_retry( #[tokio::test] async fn aws_s3_extension_import_export_round_trip() { - let server = TestServer::start().await; + // Force the postgres image to be (re)built locally so the aws_s3 + // extension files baked into this commit are present. The published + // `fakecloud-postgres:-` image only ships extensions + // that existed at the corresponding release tag; this test runs on + // pre-release commits that add aws_s3 before the next tag goes out. + let server = TestServer::start_with_env(&[("FAKECLOUD_REBUILD_POSTGRES_IMAGE", "1")]).await; let s3 = server.s3_client().await; let rds = server.rds_client().await;