feat(data-index): Pages rollout kit — 28-repo generator, consistency guards, 200-checker - #57
Merged
Merged
Conversation
…guards, 200-checker Make the relaton-data-* GitHub Pages rollout push-button and defect-proof from the support repo (relaton/relaton#48). No sibling repo is modified. - generator: add optional per-entry favicon/description/pubid_require overrides (fall back to defaults/template) and fold in the 3 already-live repos (ids/oasis/w3c) so configs.yml is the single source for all 28 sites. w3c keeps its Relaton::W3c::PubId + relaton/w3c/pubid; branch: v2 corrects their stale /main/ baseurl (index-v1.yaml is served from v2). - lib: extract baseurl helper; add pages_url / raw_index_url builders. - bin/check-data-pages: HTTP-check each repo's Pages site + raw-index, report 200, exit non-zero otherwise ("confirm each site returns 200" gate). - spec/cimas_data_pages_spec.rb: guard configs.yml <-> cimas.yml agreement (entry + data group + deploy.yml/Gemfile.deploy mapping + matching branch) to close the silent-404 class where a branch drift skips the Pages publish. - data-index/generated/: drift-guarded snapshot of all 28 rendered _config.yml. - cimas.yml: reconcile w3c/oasis/ids branch main -> v2 (verified real default). - data-index/README.adoc: finished rollout runbook + Pages-enablement status.
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.
Why
Finishes the
relaton-data-*GitHub Pages "index site" rollout (relaton/relaton#48).The per-repo machinery was correct but only wired up for 3 datasets; this makes the
rollout push-button and defect-proof from
support, with no change to anysibling repo (they're delivered via the existing Cimas + generated
_config.ymlflow).
What's here
lib/data_index_config.rb,data-index/configs.yml) — optionalper-entry
favicon/description/pubid_requireoverrides (fall back to thedefaults/template), and the 3 already-live repos (
ids,oasis,w3c) folded inso
configs.ymlis the single source for all 28 sites.w3ckeepsRelaton::W3c::PubId+relaton/w3c/pubid;branch: v2corrects their stale/main/baseurl.bin/check-data-pages— HTTP-checks each repo's Pages site + raw-index URL,reports
200, exits non-zero otherwise. The "confirm each site returns 200" gate.spec/cimas_data_pages_spec.rb— guards thatconfigs.ymlandcimas-config/cimas.ymlagree for every repo (entry +datagroup +deploy.yml/Gemfile.deploymapping + matchingbranch). Closes the silent-404class where a branch drift skips the Pages publish.
data-index/generated/— drift-guarded snapshot of all 28 rendered_config.yml(the exact bytes to commit into each data repo).cimas-config/cimas.yml— reconcilew3c/oasis/idsbranch: main -> v2(verified real default via
gh api).data-index/README.adoc— finished rollout runbook + per-repo Pages-enablementstatus (20 already enabled on
v2; 5main-default need admin).Verification
bundle exec rspec→ 169 examples, 0 failures.bin/check-data-pagesvalidated live: all 25 targets' raw-index return 200; the3 live repos return 200 site + raw-index on
v2.Not in this PR (operator steps, documented in the runbook)
cimas pushto the data repos, committing each_config.yml, enabling Pages on the5
main-default repos (needs admin), and the live 200 confirmation — all touchexternal repos / network.