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

feat: include data connections and SMTP in artifact deployment

Browse Source
This commit is contained in:
Joseph Doherty
2026-03-17 13:48:52 -04:00
parent e313eda9fd
commit 2f3e0ceecb
17 changed files with 151 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Component-Communication.md
View File

@@ -30,9 +30,9 @@ Both central and site clusters. Each side has communication actors that handle m
- Site Runtime processes the command and responds with success/failure.
- If the site is unreachable, the command fails immediately (no buffering).
### 3. System-Wide Artifact Deployment (Central → All Sites)
- **Pattern**: Broadcast with per-site acknowledgment.
- When shared scripts, external system definitions, database connections, or notification lists are explicitly deployed, central sends them to all sites.
### 3. System-Wide Artifact Deployment (Central → Site(s))
- **Pattern**: Broadcast with per-site acknowledgment (deploy to all sites), or targeted to a single site (per-site deployment).
- When shared scripts, external system definitions, database connections, data connections, notification lists, or SMTP configuration are explicitly deployed, central sends them to the target site(s).
- Each site acknowledges receipt and reports success/failure independently.
### 4. Integration Routing (External System → Central → Site → Central → External System)