Create a notification route

Only notifications whose source_id is exactly this text. At delivery today a notification's source_id is the id of the alert that fired, so a source filter matches an alert's id and nothing else. Null or a blank string is no source filter, and a blank is never stored as one. A source_id is at most 512 bytes and carries at most 4 uuids: a longer one, or one with more uuids, answers 422. A caller confined to a project may not name a source_id a route would withhold from it (NotificationRoute.source_id says which): that answers 404 Source not found, as the preview does.

Only notifications about this application (its data.application_id); null matches every application.

Only notifications about a branch, tag or pull request matching this glob (data.reference): main or refs/heads/main for the main branch, release/* within one path segment, release/** across segments, pull/* for every pull request, refs/tags/v* for tags. A pull request targeting main does not match main. Null matches every reference.

Pin the route to a project: it delivers only that project's notifications. Absent pins it to the caller's current project (a token pinned to a project always stamps that project); null makes it organisation-wide, which takes alerts.manage at organisation scope.

Only notifications about this cluster; null matches every cluster. A caller confined to a project reads a cluster outside that project as null, and the route then carries scope_note.

Only notifications whose source_id is exactly this text; null matches every source. At delivery today a notification's source_id is the id of the alert that fired, so a source filter matches an alert's id and nothing else. A caller confined to a project reads a source_id as null, and the route then carries scope_note, when any id in it, the whole source_id or one part of a composite one such as <cluster>/<node group> or <repository>:<ref>, names a cluster, application, ticket, pipeline run or step, pipeline repository, automation, workspace, incident, environment or API token of another project or of no project, an execution, power schedule, application installation, sandbox environment, agent task or support ticket on such a cluster, or an alert a rule of which names a cluster outside the caller's project, or that is deleted; and when it is longer than 512 bytes or carries more than 4 uuids, which no write accepts any more. Any other source_id is shown as written. The note names no id, but it does tell the reader that an id it already holds is outside its project, as a 404 Source not found from the preview or a route write does.

Only notifications about this application (its data.application_id); null matches every application. A caller confined to a project reads an application outside that project as null, and the route then carries scope_note.

Only notifications about a branch, tag or pull request matching this glob (data.reference): main or refs/heads/main for the main branch, release/* within one path segment, release/** across segments, pull/* for every pull request, refs/tags/v* for tags. A pull request targeting main does not match main. Null matches every reference. It is shown as written to every caller, one confined to a project included: no project holds a glob over branch and tag names.

The project the route is pinned to: it delivers only that project's notifications, read from the ticket, application, pipeline run, repository, automation, workspace, incident, environment or cluster the notification is about. Null is organisation-wide: the route hears every project's notifications and the organisation's own.

Set only when a cluster_id, application_id or source_id filter of this route is withheld from a caller confined to a project: that field reads as null, and this note says the null does not mean every cluster, application or source. Absent otherwise.