fix: Add become: true to all playbooks#58
Merged
john-derose merged 2 commits intomasterfrom Mar 1, 2026
Merged
Conversation
Under the user-owned path model, playbooks run as the homestak user instead of root. All playbooks that modify system files need become: true to escalate via sudo. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
john-derose
approved these changes
Mar 1, 2026
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
2 participants
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.
Summary
become: trueto all 6 playbooks missing ithomestakuser and needs sudo escalation for system file modifications (apt, /etc/hosts, systemd, etc.)Files changed
pve-install-kernel.yml,pve-install-packages.yml,pve-install.ymlpve-setup.yml,user.yml,config-apply.ymlTest plan
homestak pve-setupsucceeds as homestak user on mother🤖 Generated with Claude Code