Repository navigation
Agent self-update: make Latest the default - #2078
Merged
Merged
Conversation
Admins expect hosts to update their own client, as the legacy FOG Client does. Self-update should have been on by default when it was added, and it was not. FOG_AGENT_UPDATE_MODE now defaults to Latest instead of Off. - Schema step 456 moves a stored Off to Latest, including an Off chosen on purpose. A fresh install reaches Latest the same way. Pinned and Latest are left alone. - Update rings (default 0,3,7) still pace the rollout. - A server with no internet access now logs one failed release sync per hour until Off is set; nothing else changes for its agents. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…te-default-latest-dev # Conflicts: # packages/web/commons/schema.php
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
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.
Admins expect hosts to update their own client, as the legacy FOG Client does. Self-update should have been on by default when it was added, and it was not.
FOG_AGENT_UPDATE_MODEnow defaults to Latest instead of Off.Release note: this enables fog-agent auto-updates by default. The upgrade moves every server set to Off to Latest, including an Off chosen on purpose. To keep updates off, set
FOG_AGENT_UPDATE_MODEback to Off under FOG Configuration after the upgrade. Update rings (default 0,3,7 days) pace the rollout.offtolatest. A fresh install reaches Latest the same way. Pinned and Latest stay as they are.Tests: schema-gate, schema-upgrade-replay, schema-manifest-consistent, agent-update-rings, agent-update-state, installer-schema-deploy pass. No DB test covers the flip itself (
schema-executesskips withoutFOG_TEST_DSN).Docs: FOGProject/fog-docs#216, FOGProject/fog-agent#42. Replaces #2076, which targeted working-1.6 by mistake.
🤖 Generated with Claude Code