fix(seed): seed Engineering Alerts notification list on both stacks

Test instances persistently emit Notify.To("Engineering Alerts").Send;
without the list at central a fresh cutover parks every notification
(observed 42k+ parked in a 3.5-min S&F drain after the rename).
Mirror the seed across docker/seed-sites.sh and docker-env2/seed-sites.sh.
This commit is contained in:
Joseph Doherty
2026-05-28 10:20:02 -04:00
parent d73f1b103a
commit de05c65992
2 changed files with 14 additions and 0 deletions
+7
View File
@@ -32,6 +32,13 @@ $CLI $URL $AUTH site create \
--grpc-node-b-address "http://scadabridge-env2-site-x-b:8083" \
|| echo " (Site-X may already exist)"
echo ""
echo "Creating Engineering Alerts notification list..."
$CLI $URL $AUTH notification create \
--name "Engineering Alerts" \
--emails "engineer@company.com" \
|| echo " (Engineering Alerts may already exist)"
echo ""
echo "Seeding LDAP group mappings (Design + Deployment)..."
# SecurityConfiguration.HasData declares 4 mappings but the InitialSchema
+7
View File
@@ -56,6 +56,13 @@ $CLI $URL $AUTH site create \
--grpc-node-b-address "http://scadabridge-site-c-b:8083" \
|| echo " (Site-C may already exist)"
echo ""
echo "Creating Engineering Alerts notification list..."
$CLI $URL $AUTH notification create \
--name "Engineering Alerts" \
--emails "engineer@company.com" \
|| echo " (Engineering Alerts may already exist)"
echo ""
echo "Seeding LDAP group mappings (Design + Deployment)..."
# SecurityConfiguration.HasData declares 4 mappings but the InitialSchema