[OpenNMS/opennms] 283afc: NMS-20268: fix specific-date padding, gate applies...
joseanesONMS via opennms-cvs <[email protected]>
| Newsgroups | gmane.network.opennms.cvs |
|---|---|
| Message-ID | <OpenNMS/opennms/push/refs/heads/jira/NMS-20268-scheduled-outages/[email protected]> |
Branch: refs/heads/jira/NMS-20268-scheduled-outages
Home: https://github.com/OpenNMS/opennms
Commit: 283afc3225844cc17749f48f1a4c59c27f6b8942
https://github.com/OpenNMS/opennms/commit/283afc3225844cc17749f48f1a4c59c27f6b8942
Author: Jose Anes <[email protected]>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M opennms-webapp/src/main/webapp/WEB-INF/applicationContext-spring-security.xml
M ui/src/components/ScheduledOutages/TimeSpanEditor.vue
M ui/src/components/ScheduledOutages/outageTime.ts
M ui/src/containers/ScheduledOutageEditor.vue
M ui/src/containers/ScheduledOutages.vue
M ui/src/services/scheduledOutagesService.ts
M ui/tests/components/ScheduledOutages/outageTime.test.ts
M ui/tests/services/scheduledOutagesService.test.ts
Log Message:
-----------
NMS-20268: fix specific-date padding, gate applies-to, harden the editor
Review of the Vue rewrite surfaced a set of defects now fixed:
- Specific-date day used unpadded 1..31, so a single-digit day produced a
19-char begins/ends string that BasicScheduleUtils (which keys the parser on
length) silently misread as a daily span — a one-time window became a
permanent outage. The specific-date field now uses zero-padded 01..31; the
monthly day attribute keeps the unpadded 1..31 the parser expects.
- The applies-to GET endpoints are now admin-gated in spring security so a
read-only user can't enumerate poller/collectd/threshd package names.
- Autocomplete queries are stripped of FIQL/URL metacharacters before being
interpolated into the _s filter.
- Editor: changing the outage type or "select all" now confirms before
discarding entered spans/selection; a partial membership-save failure
re-reads the actual state instead of leaving a stale snapshot; duplicate
time spans and failed deletes now surface a message; a failed list load
keeps the previous rows instead of blanking the table.
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