Skip to content

fix(staging): pin website liveness probe to port 4000 - #1116

Open
think-back wants to merge 1 commit into
mainfrom
fix/staging-website-liveness-main
Open

think-back wants to merge 1 commit into
mainfrom
fix/staging-website-liveness-main

Conversation

@think-back

Copy link
Copy Markdown
Collaborator

Summary

  • explicitly set the staging website Cloud Run liveness probe to port 4000
  • prevent inherited port 8080 drift from restarting healthy staging instances

Scope

  • one staging deployment workflow line only
  • no frontend UI or copy changes
  • no backend, database, Stripe, entitlement, or production service changes

Verification

  • equivalent change is merged on staging
  • staging workflow succeeded
  • latest staging revision serves 100% traffic with liveness on port 4000

Constraint: The staging website listens on port 4000 while Cloud Run had inherited a stale liveness port.
Rejected: Rely on Terraform to repair the probe | The service lifecycle intentionally ignores probe changes.
Confidence: high
Scope-risk: narrow
Directive: Keep the staging deploy probe aligned with the website container port.
Tested: staging workflow deployment succeeded with liveness on port 4000; git diff --check
Not-tested: Main is not deployed by this staging-only workflow change
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