v0.13.1

v0.13.1

Patch release on the v0.13.0 train shipping two RDS infra additions.

What's new

PostgreSQL aws_lambda extension

SQL inside fakecloud-managed PostgreSQL DB instances can now invoke
fakecloud Lambda functions, matching AWS RDS / Aurora's documented
surface (and LocalStack's):

CREATE EXTENSION IF NOT EXISTS aws_lambda CASCADE;
SELECT aws_lambda.invoke(
  aws_commons.create_lambda_function_arn('my-fn'),
  '{"hello": "world"}'::json
);

A plpython3u UDF posts to a new /_fakecloud/rds/lambda-invoke
bridge that resolves the function ARN against the fakecloud Lambda
service. Works with any Lambda runtime supported by fakecloud.

Prebuilt fakecloud-postgres images

CreateDBInstance no longer pays the ~60s apt install plpython3u
build on first use. Per release, we publish four multi-arch
(linux/amd64 + linux/arm64) images:

• ghcr.io/faiscadev/fakecloud-postgres:13-0.13.1 (and rolling :13)
• ghcr.io/faiscadev/fakecloud-postgres:14-0.13.1 (and rolling :14)
• ghcr.io/faiscadev/fakecloud-postgres:15-0.13.1 (and rolling :15)
• ghcr.io/faiscadev/fakecloud-postgres:16-0.13.1 (and rolling :16)

Runtime resolves images pull-first (docker image inspect ->
docker pull -> local build). Local build remains as the offline
/ unreleased / dev fallback, so airgapped setups keep working.

Override the registry with FAKECLOUD_POSTGRES_REGISTRY=.... Force
a fresh local rebuild with FAKECLOUD_REBUILD_POSTGRES_IMAGE=1.

Upgrade notes

• No breaking changes. v0.13.1 is drop-in over v0.13.0.
• Existing v0.13.0 deployments don't get the prebuilt-image speedup
  retroactively (the :<major>-0.13.0 tag was not backfilled).
  Upgrade to v0.13.1 to pick it up.

PRs

• #802 feat(rds): support PostgreSQL aws_lambda extension
• #803 feat(rds): publish prebuilt fakecloud-postgres images, pull-first runtime
• #804 ci(rds): PR dry-run + workflow_dispatch test path for image publish
• #805 release(v0.13.1)

Full Changelog: v0.13.0...v0.13.1