As part of the deployment workflow, implement the following:
scap rollback
- Present user staging history via scap prep --history
- Hard reset the git state on the deployment server
- scap sync-world
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T198901 Migrate production services to kubernetes using the pipeline | |||
| Resolved | Clement_Goubert | T238770 Deploy MediaWiki to Wikimedia production in containers | |||
| Resolved | None | T279322 Design m8s deployment workflows and tooling | |||
| Resolved | dduvall | T287045 Scap rollback command |
Event Timeline
Comment Actions
Need to rethink this since the image tag won't be updated via the deployment-charts repo.
Comment Actions
Putting this up for grabs since I'll be out on vacation for the remainder of the week.
Upon investigation, implementing scap rollback will probably duplicate a lot of what scap prep auto --history already does, so I think we should probably just implement the revert functionality in the latter and possibly create a scap rollback subcommand that aliases scap prep auto --history --revert or something like that.
I did have a change to modify AbstractSync to mark the latest history entry as synced, so I'll throw that up. I have not had a chance to test it, however.
Comment Actions
Change 805496 had a related patch set uploaded (by Dduvall; author: Dduvall):
[mediawiki/tools/scap@master] history: Mark latest history entry as synced following any sync command
Comment Actions
Change 808086 had a related patch set uploaded (by Dduvall; author: Dduvall):
[mediawiki/tools/scap@master] rollback: Provide rollback subcommand for quick history replay and sync
Comment Actions
Change 805496 merged by jenkins-bot:
[mediawiki/tools/scap@master] history: Mark latest history entry as synced following any sync command
Comment Actions
Change 808086 merged by jenkins-bot:
[mediawiki/tools/scap@master] rollback: Provide rollback subcommand for quick history replay and sync