tailscale-policy: split SSH rule because autogroup:self is illegal with tag src #142
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#142
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
terraform applyrejected with two cascading errors:autogroup:selfis the "this user's own devices" selector and is only legal when src is a user. Tagged devices have no user (their owner is the meta-usertagged-devices), so the ruleadded in coilysiren/infrastructure#139 is rejected by the API. The device-tag failures cascade from this: the rejected ACL means the new
tag:physical/ per-hosttagOwnersnever landed, so thetailscale_device_tagsAPI can't recognize them either.Change
Split the combined SSH rule in
terraform/tailscale-policy/main.tfback into two:autogroup:member→[autogroup:self, tag:server](unchanged from pre-IaC)tag:physical→[tag:server]only (no autogroup:self - illegal for tag-src)Tagged client physicals lose SSH-out to other client physicals' own-user devices but keep SSH-out to kai-server, which is the practical case.
Filed by Claude.