VersionControl:PRs/maybelle-config/283: Difference between revisions

From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
DrivingThatTrain (talk | contribs)
cryptograss/maybelle-config#283, as GitHub has it
 
DrivingThatTrain (talk | contribs)
cryptograss/maybelle-config#283, as GitHub has it
 
Line 16: Line 16:
|deploy=
|deploy=
}}
}}
<pre class="pr-body">Finishing the push (magenta#404, pickipedia#175, #279). #279 gave memory-lane `WIKI_HOOK_SECRET` from the vault's `memory_lane_wiki_hook_secret`; the wiki's side, `$wgPickiPediaContentMagentaHookSecret`, was to be set "in LocalSettings.local.php on the wiki host". That file is written by this deploy from the vault (two tasks, both to the Jenkins secrets dir), so a hand edit there is overwritten on the next run, and the no-touch rule says not to anyway.
This adds the line to both templates, from the same vault value, guarded by `is defined` like the others. Nothing else changes.
Order after merging: redeploy maybelle (writes the file, and gives memory-lane the secret and magenta#414's pulse), then pickipedia (its build copies the file in), then hunter (the poller of #414). The first push shows on https://magenta.cryptograss.live/wiki-hooks/ as "heard".
Redeploy maybelle, then pickipedia, then hunter.
Worked on by: magent and justin, in #interfaces</pre>

Latest revision as of 17:06, 9 November 2026

maybelle-config#283: pickipedia: the push's secret reaches the wiki from the vault
State 🟣 merged 2026-11-07 02:30:05
Worked on by magent, justin
Moods #interfaces
Deploy not said
Branch wiki-hook-secret-wiki → production, by magent-cryptograss
Opened · last pushed 2026-11-07 02:27:08 · 2026-11-07 02:27:04
Finishing the push (magenta#404, pickipedia#175, #279). #279 gave memory-lane `WIKI_HOOK_SECRET` from the vault's `memory_lane_wiki_hook_secret`; the wiki's side, `$wgPickiPediaContentMagentaHookSecret`, was to be set "in LocalSettings.local.php on the wiki host". That file is written by this deploy from the vault (two tasks, both to the Jenkins secrets dir), so a hand edit there is overwritten on the next run, and the no-touch rule says not to anyway.

This adds the line to both templates, from the same vault value, guarded by `is defined` like the others. Nothing else changes.

Order after merging: redeploy maybelle (writes the file, and gives memory-lane the secret and magenta#414's pulse), then pickipedia (its build copies the file in), then hunter (the poller of #414). The first push shows on https://magenta.cryptograss.live/wiki-hooks/ as "heard".

Redeploy maybelle, then pickipedia, then hunter.
Worked on by: magent and justin, in #interfaces