dohertj2/scadalink-design
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs(notification-outbox): merge duplicate S&F dependency bullet, standardize cross-ref

Browse Source
This commit is contained in:
Joseph Doherty
2026-05-18 23:48:59 -04:00
parent bb35453d58
commit c8b8cd9150
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/requirements/Component-DeploymentManager.md
View File

@@ -110,9 +110,10 @@ A deployment to a site includes the flattened instance configuration plus any sy
System-wide artifact deployment is a **separate action** from instance deployment, triggered explicitly by a user with the Deployment role. Artifacts can be deployed to all sites at once or to an individual site (per-site deployment via the Sites admin page). System-wide artifact deployment is a **separate action** from instance deployment, triggered explicitly by a user with the Deployment role. Artifacts can be deployed to all sites at once or to an individual site (per-site deployment via the Sites admin page).
Notification lists and SMTP configuration are **not** deployable artifacts — they Notification lists and SMTP configuration are **not** deployable artifacts — they
are central-only definitions managed by the Notification Service. Notification are central-only definitions managed by the Notification Service (see
delivery happens on the central cluster (see Component-NotificationOutbox.md), so Component-NotificationService.md). Notification delivery happens on the central
no notification artifact or SMTP credential is ever distributed to sites. cluster, so no notification artifact or SMTP credential is ever distributed to
sites.
## Site-Side Apply Atomicity ## Site-Side Apply Atomicity

3
docs/requirements/Component-SiteRuntime.md
View File

@@ -354,9 +354,8 @@ Per Akka.NET best practices, internal actor communication uses **Tell** (fire-an
## Dependencies ## Dependencies
- **Data Connection Layer**: Provides tag value updates to Instance Actors. Receives write requests from Instance Actors. - **Data Connection Layer**: Provides tag value updates to Instance Actors. Receives write requests from Instance Actors.
- **Store-and-Forward Engine**: Handles reliable delivery for external system calls, notifications, and cached database writes submitted by scripts. - **Store-and-Forward Engine**: Handles reliable delivery for external system calls, cached database writes, and notifications submitted by scripts. For the notification category specifically, it forwards to the central cluster for delivery (not directly to SMTP).
- **External System Gateway**: Provides external system method invocations for scripts. - **External System Gateway**: Provides external system method invocations for scripts.
- **Store-and-Forward Engine**: Carries script-generated notifications to the central cluster for delivery (the notification category targets central, not SMTP).
- **Communication Layer**: Receives deployments and lifecycle commands from central. Handles debug view requests. Reports deployment results. - **Communication Layer**: Receives deployments and lifecycle commands from central. Handles debug view requests. Reports deployment results.
- **Site Event Logging**: Records script executions, alarm events, deployment events, instance lifecycle events. - **Site Event Logging**: Records script executions, alarm events, deployment events, instance lifecycle events.
- **Health Monitoring**: Reports script error rates and alarm evaluation error rates. - **Health Monitoring**: Reports script error rates and alarm evaluation error rates.