Skip to content

fix: drop maxShutdownDelaySeconds from Render Blueprint - #51

Merged
quangshuynh merged 1 commit into
mainfrom
fix/render-blueprint-shutdown-delay
Sep 27, 2026
Merged

quangshuynh merged 1 commit into
mainfrom
fix/render-blueprint-shutdown-delay

Conversation

@quangshuynh

Copy link
Copy Markdown
Owner

Render's Blueprint validation rejects render.yaml with:

services[0].maxShutdownDelaySeconds
max shutdown delay is not supported for services with a disk

Change

  • Remove only maxShutdownDelaySeconds: 30 from the flipper-app service. Render's default graceful shutdown delay is 30 seconds when omitted, so shutdown behavior is unchanged.
  • Update the one deployment-doc sentence that named the field.

Start command, Uvicorn --timeout-graceful-shutdown 20, disk, plan, region, instances, health check, env vars, and secrets are untouched. No tests referenced the field.

Verification

  • pytest tests/test_deployment.py: 12 passed, 1 skipped
  • pytest: 802 passed, 4 skipped
  • ruff check . / ruff format --check .: clean
  • mkdocs build --strict: clean
  • git diff --check: clean

Nothing deployed; no Render resources or databases touched.

Render rejects maxShutdownDelaySeconds for services with a persistent disk.
The omitted setting defaults to a 30-second graceful shutdown delay, so
behavior is unchanged; Uvicorn still drains for up to 20 seconds.
@quangshuynh
quangshuynh merged commit 47274c4 into main Sep 27, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant