Verify WUD notifications reach ntfy #15

New issue

Open

opened 2026-08-23 17:07:53 +00:00 by stanta · 0 comments

stanta commented

2026-08-23 17:07:53 +00:00

Owner

Outcome

Prove that a controlled WUD update event reaches the current ntfy notification path.

Current state

WUD is deployed and ntfy delivery exists, but their end-to-end integration needs a recorded validation.

Work

Inspect the configured WUD notification path without exposing credentials.
Trigger a safe controlled update event.
Confirm delivery and useful message content.
Confirm failure behavior is visible.

Validation

The controlled event appears in ntfy.
The notification identifies the host, image, current tag, and candidate tag.
No secret appears in logs or messages.

References

iac/guides/roadmap-phase-2.md
iac/ansible/roles/services_infra/
iac/ansible/roles/ntfy/

## Outcome Prove that a controlled WUD update event reaches the current ntfy notification path. ## Current state WUD is deployed and ntfy delivery exists, but their end-to-end integration needs a recorded validation. ## Work - [ ] Inspect the configured WUD notification path without exposing credentials. - [ ] Trigger a safe controlled update event. - [ ] Confirm delivery and useful message content. - [ ] Confirm failure behavior is visible. ## Validation - [ ] The controlled event appears in ntfy. - [ ] The notification identifies the host, image, current tag, and candidate tag. - [ ] No secret appears in logs or messages. ## References - `iac/guides/roadmap-phase-2.md` - `iac/ansible/roles/services_infra/` - `iac/ansible/roles/ntfy/`

stanta added the

labels

2026-08-23 17:07:53 +00:00