fix(restic): use %N so the alert unit is not named .service.service #922
No reviewers
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!922
Loading…
Reference in a new issue
No description provided.
Delete branch "ops/917-alert-unit-name"
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?
Cosmetic follow-up to #921, caught while verifying the rollout on ser8.
%nkeeps the unit type suffix, soOnFailure=restic-failure-alert@%n.serviceinstantiated:It works. Verified on ser8 (systemd 259): the unit resolves,
%ibecomesrestic-prune.service, and the handler runs tostatus=0/SUCCESS. But the name reads like a bug to anyone who meets it insystemctloutput or a journal line, which is a bad property for something only ever seen during an incident.%Nis the same specifier without the suffix. The handler passes%itosystemctl, which appends.serviceitself, so the script needs no change.pre-commit run --all-filesgreen.🤖 Generated with Claude Code