Files
pipelines/docs/notes/notification-web-links.md
T

32 lines
1.9 KiB
Markdown

# Notification web run links
Run-attention/completion notifications and stage hooks now use
`PIPELINES_WEB_PUBLIC_URL` to build `<origin>/runs/<id>` links to the authenticated
web app. This is an operator-controlled origin, not an inferred API/ntfy host.
Credentials, queries, fragments and subpaths are rejected; invalid configuration
omits the link with a diagnostic. Existing Android-only deployments without this
setting retain their original scheme. Already-sent notifications are unchanged.
Native setup saves its advertised web address by default and retains explicit
origin overrides across reinstalls. Custom service generation preserves the
variable; Docker Compose forwards it. Authenticated proxy login already preserves
the target run and is covered by a new isolated HTTP regression.
Verified: full Go race suite, build/vet, installer unit tests, stage-hook web links
(including attachments), waiting/failed run web payloads, URL validation and
service-environment retention on both renderers. The isolated real proxy test
checks unauthenticated gating, wrong-password rejection and return to the exact
run after login. No production notification was sent to test this fix.
The operator supplied `https://alans-macbook-pro.tail6bf4dc.ts.net:8443/pipelines`;
the configured origin excludes the pipeline-list route. Deployment was authorized.
The first live check (#23) exposed a missing transactional-outbox path: the store
had already enqueued a legacy link before the server callback, so an insert-only
callback did not change it. Dispatch now resolves that placeholder to the
configured web link (also after restart), and the completed receipt saves the
actual target used. Added real FinishRun/outbox and failed-publication/reopen
regressions. Previously sent alerts are not modified or resent.
Dummy runs #22 and #23 completed with their old Android-link notifications
acknowledged by ntfy. Those verify publishing, not correct web navigation.