Repository navigation
TIGER-331: auto-update on install — enableAll() + update:auto / update:apply (v1.24.0) - #342
Merged
Merged
Conversation
…apply (v1.24.0) A fresh install never enrolled anything into the WP-style `update.autoupdate` opt-in, so nothing auto-applied. Add the "keep this install current" switch provisioning flips, built on the existing machinery (no bespoke updater): - Tiger_Update_AutoUpdate::enableAll(bool $includeCore=true) / disableAll(): enroll `tiger-core` + every installed module (bySlugMap) + every skill (installed()), network-free, merged + written once. $includeCore=false is the control-plane case (core stays deploy-driven on a booting ASG member). - bin/tiger: `update:auto on|off|list [<slug>|--all] [--modules-only]` and `update:apply --auto` (the immediate pass = runScheduledAutoUpdates()). The console boot runs module bootstraps, so System_Service_Updates autoloads. The firstboot (golden images) and the headless installer (every Tiger install) call these; see TigerDen/TigerHeadless. Tests cover enroll-all (merges + core + idempotent), --modules-only, and disableAll. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ASauLLscjqdsNqBNsx2Typ
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.
What
A freshly provisioned box never enrolled anything into the WP-style
update.autoupdateopt-in, so nothing auto-applied. This adds the "keep this install current" switch that provisioning flips — built entirely on the existing update machinery (Tiger_Update_AutoUpdate+System_Service_Updates::runScheduledAutoUpdates+ the dailysystem.update_checkjob). No bespoke updater.Changes (this PR — the core engine)
Tiger_Update_AutoUpdate::enableAll(bool $includeCore = true)/disableAll()— enrolltiger-core+ every installed module (bySlugMap) + every skill (installed()), network-free, merged with anything already on, written once.$includeCore = falseis the control-plane case (core stays deploy-driven on a booting ASG member).bin/tigerverbs:update:auto on|off|list [<slug>|--all] [--modules-only]andupdate:apply --auto(the immediate pass). The console boot runs module bootstraps, soSystem_Service_Updatesautoloads.--modules-only, anddisableAll.Consumers (separate repos, follow-on)
update:auto on --all+update:apply --auto(best-effort).autoupdateinstall step (in-process, no-shell-safe) → every Tiger install.AutoLaunch::_waitFirstboot300→600s for the heavier firstboot.tiger update:auto on --all --modules-onlyas a controlled-deploy step (not boot).🤖 Generated with Claude Code
https://claude.ai/code/session_01ASauLLscjqdsNqBNsx2Typ