Skip to content

chore(infra): delete the GitHub staging keepalive now that the Cloudflare pinger is proven - #682

Merged
thomasluizon merged 1 commit into
mainfrom
chore/ticket-1009-drop-keepalive
Oct 1, 2026
Merged

thomasluizon merged 1 commit into
mainfrom
chore/ticket-1009-drop-keepalive

Conversation

@thomasluizon

Copy link
Copy Markdown
Owner

Deletes .github/workflows/staging-keepalive.yml, the scheduled GitHub workflow that pinged the staging API, now that the Cloudflare Worker orbit-staging-pinger is proven. infra/README.md drops the "keep the workflow until the proof is recorded" sentences and names the Worker as the only staging keepalive.

Closes thomasluizon/orbit-tickets#1009

Test evidence

  • Seven independent probes, ten minutes apart, inside the 11:00 to 02:59 UTC window (2026-10-01T21:40:15Z to 22:40:17Z): every one returned 200 with curl_exit=0, durations 0.207 to 0.521 seconds (the full table is on the ticket).
  • Worker Observability (last 3 hours): one scheduled invocation every five minutes with no gap from 20:55 to 22:55 UTC, 25 invocations, 0 errors; all 13 slots of the probe hour are present, and the sampled event reads outcome: ok, wallTimeMs: 143.
  • git grep keepalive returns only the README line naming the Worker as the keepalive.

Assumptions

  • None.

Manual steps

  • None. The Worker and both cron schedules are already applied.

🤖 Generated with Claude Code

…lare pinger is proven

The orbit-staging-pinger Worker ran every five minutes through a full
observation hour with all seven independent probes under two seconds,
so the scheduled GitHub workflow is redundant.

Refs thomasluizon/orbit-tickets#1009

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes Review covered the complete workflow deletion and documentation update, including the existing Cloudflare replacement and recorded cutover evidence.

  • Workflow removal: Deletes the GitHub staging health-ping schedule; the existing Worker preserves the same endpoint, five-minute cadence, and operating window.
  • Operational guidance: Identifies the Worker as the sole staging keepalive and requires repeating the observation after changes to its code or schedules.

Verification: node --test infra/staging-pinger.test.mjs passed all 15 tests, and no references to the deleted workflow remain. Cutover assessment relies on the probe and Worker invocation evidence recorded in the PR; the linked ticket's full table was inaccessible to this run (HTTP 404), and live Cloudflare history was not independently inspected.

Pullfrog  | View workflow run | Using gpt-6.1-sol | 𝕏

@sonarqubecloud

sonarqubecloud Bot commented Oct 1, 2026

Copy link
Copy Markdown

@thomasluizon
thomasluizon merged commit c04451f into main Oct 1, 2026
27 checks passed
@thomasluizon
thomasluizon deleted the chore/ticket-1009-drop-keepalive branch October 1, 2026 23:56
thomasluizon added a commit that referenced this pull request Oct 2, 2026
* chore(infra): delete the GitHub staging keepalive now that the Cloudflare pinger is proven (#682)

The orbit-staging-pinger Worker ran every five minutes through a full
observation hour with all seven independent probes under two seconds,
so the scheduled GitHub workflow is redundant.

Refs thomasluizon/orbit-tickets#1009

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c04451f)

* fix: control reminder scheduler test clocks (#1018) (#683)

(cherry picked from commit b2af4c8)

* Retire Resend and require Amazon SES (#684)

* Remove retired email transport and require SES at startup

* Retire obsolete email configuration and DNS declarations

* Configure SES in infrastructure startup test fixtures

* docs(infra): release the SES-only build before retiring email settings

An old build falls back to Resend when Email__Provider is absent, and
Render's Save and deploy redeploys the existing build, so the cleanup
now runs only after both environments run and verify the SES-only build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 310a552)

# Conflicts:
#	tests/Orbit.Infrastructure.Tests/Services/ResendEmailServiceTests.cs

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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