[OpenNMS/opennms] 4af103: NMS-20100: route the path test to v1 and persist s...

  Branch: refs/heads/jira/NMS-20100
  Home:   https://github.com/OpenNMS/opennms
  Commit: 4af103ab555a6847e76c98970b9b2785e21ea277
      https://github.com/OpenNMS/opennms/commit/4af103ab555a6847e76c98970b9b2785e21ea277
  Author: Jose Anes <[email protected]>
  Date:   2026-08-28 (Fri, 28 Aug 2026)

  Changed paths:
    M opennms-config/src/main/java/org/opennms/netmgt/config/NotificationManager.java
    M opennms-webapp-rest/src/test/java/org/opennms/web/rest/v2/NotificationConfigRestServiceIT.java
    M ui/src/services/notificationConfigService.ts
    A ui/tests/services/notificationConfigService.test.ts

  Log Message:
  -----------
  NMS-20100: route the path test to v1 and persist severity on update !smoke

The destination-path Test button posted to /api/v2, but the trigger endpoint
only exists on the v1 NotificationRestService, so every test 404ed into the
generic failure snackbar. The service now posts via the v1 rest instance, and
a service test pins the instance and path.

NotificationManager.replaceNotification copied twelve fields but never
setEventSeverity, so editing or clearing the severity of an existing
notification silently reported success while changing nothing. The copy now
carries it, and the config REST IT covers set, change, and clear on update.



To unsubscribe from these emails, change your notification settings at https://github.com/OpenNMS/opennms/settings/notifications


_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/wiki/index.php?page=MailingListFaq
opennms-cvs mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-cvs