storm-impact-harmonisation: retire cerf-rr slot, record merged trunk - #511
Open
zackarno wants to merge 1 commit into
Open
storm-impact-harmonisation: retire cerf-rr slot, record merged trunk#511zackarno wants to merge 1 commit into
zackarno wants to merge 1 commit into
Conversation
The CERF predictor deployment this page listed as live no longer exists. The app was ported to ds-cerf-3rm-app (already its own KB page) and the chd-ds-seas5-viz/cerf-rr slot was deleted from Azure on 2026-08-03, recorded as ADR 0006 in the source repo. Verified at the time: the replacement returns HTTP 200 while the old slot returned 503. Only that slot was deleted — the development slot and production site of chd-ds-seas5-viz belong to ds-seas5-viz and are untouched. Also brings the page in line with the repo as it now is: - branch_split described three unmerged feature branches and a main that carried only workflow triggers. All were merged into main on 2026-08-03 and deleted, so that note is replaced with the resolved layout. The one deliberate exception, gdacs-adam-data, is called out with its ADR 0004 rationale so nobody "tidies" it away. - The duplicate branch_note describing the same (now removed) ref: workaround is dropped. - Adds the PDC cyclone poll (3-hourly) and its raw blob output; PDC serves no archive and no track history, so that record only exists going forward. - The global-cyclones deploy is now dispatch-only, not push-triggered. - Flags app/cerf_predictor.py as a deployment-less duplicate that will drift, pointing at ds-cerf-3rm-app as source of truth, on both pages.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The KB listed a CERF predictor deployment that no longer exists, and described a branch layout that was resolved today.
What changed in the world
The
cerf-rrslot is gone. The CERF predictor was ported tods-cerf-3rm-app(which already has its own KB page). The deploy workflow inds-storm-impact-harmonisationwas deleted and thechd-ds-seas5-viz/cerf-rrslot removed from Azure on 2026-08-03, recorded as ADR 0006 in the source repo.Verified before deleting: the replacement
https://cerf-3rm.azurewebsites.netreturned HTTP 200 while thecerf-rrslot returned HTTP 503. Only that slot was deleted — thedevelopmentslot and production site ofchd-ds-seas5-vizbelong tods-seas5-vizand were confirmed untouched afterwards.The trunk split is resolved. The page's
branch_splitnote described three unmerged feature branches withmaincarrying only workflow triggers that checked those branches out at runtime. All were merged intomain(PR #3) and deleted the same day.Changes
pipelines/storm-impact-harmonisation.mdbranch_split→ resolvedbranch_layout; duplicate stalebranch_notedropped; PDC poll + its blob output added; global-cyclones deploy corrected to dispatch-only;source_branch→maininfrastructure/deployments.mdapps/cerf-3rm-app.mdpredecessornote recording what it supersedesDeliberately preserved
gdacs-adam-datais called out explicitly in the newbranch_layoutas the one branch kept unmerged on purpose (ADR 0004 retired the dashboard by closing PR #2 without merging, and keeps the branch as the only place that dashboard exists). Recorded so nobody tidies it away later.Both pages' YAML frontmatter validated.