Skip to content

NMS-20100: Destination Paths tab - #8707

Closed
joseanesONMS wants to merge 2 commits into
OpenNMS:developfrom
joseanesONMS:jira/NMS-20100-destination-paths
Closed

NMS-20100: Destination Paths tab#8707
joseanesONMS wants to merge 2 commits into
OpenNMS:developfrom
joseanesONMS:jira/NMS-20100-destination-paths

Conversation

@joseanesONMS

Copy link
Copy Markdown
Contributor

Adds the Destination Paths tab to the Configure Notifications dialog. Depends on #8693 (the base Notifications page PR); review the last commit only until that merges.

  • Tab with the path list and a test-trigger action.
  • Editor covering initial delay, targets (users, groups, on-call roles, email addresses) with per-target commands, intervals and auto-notify, and escalations; the Browser notification method is selectable end to end.
  • /rest/notification-config destination-path mutations, commands and on-call-roles endpoints wrap the same destinationPaths.xml, notificationCommands.xml and groups.xml factories the legacy wizard uses; a path rename follows into the event notifications that reference it.
  • GroupManager rebuilds its role map on every parse so removing the last role in groups.xml is not masked by a stale cache.

Rewrites the Notifications page (notice queries, outstanding/acknowledged
notice lists with CSV export and printing, collapsible explanations) as a
PrimeVue page backed by REST, and adds a Configure Notifications dialog
holding a General tab with the system-wide notification on/off switch.

Adds the admin-only /rest/notification-config endpoints for the notifd
status and the read side of destination paths (the base API surface for the
dependent tab PRs), backed by the same file-backed factories the legacy
wizards use — the XML files stay the system of record. Browser delivery of
notices for /ui pages ships here as well. The Event Notifications,
Destination Paths and Path Outages tabs follow in dependent PRs.
Adds the Destination Paths tab: path list with a test-trigger action, and
an editor covering initial delay, targets (users, groups, on-call roles,
email addresses) with per-target commands, intervals and auto-notify, and
escalations — the Browser notification method is selectable end to end.
The /rest/notification-config destination-path mutation, commands and
on-call-roles endpoints wrap the same destinationPaths.xml,
notificationCommands.xml and groups.xml factories the legacy wizard uses.
GroupManager now rebuilds its role map on every parse so removing the last
role in groups.xml is not masked by a stale cache.
Depends on the Notifications page base PR.
@joseanesONMS
joseanesONMS force-pushed the jira/NMS-20100-destination-paths branch from 7e29d37 to bfc0f5e Compare July 30, 2026 20:26
@joseanesONMS

Copy link
Copy Markdown
Contributor Author

Replaced by #8711 (NMS-20119, in-repo stacked on #8709).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant