Move the messaging out of the transaction

server/lib/blueprints/applyBlueprint.ts

@@ -1,5 +1,6 @@
 import {
     db,
+    primaryDb,
     newts,
     blueprints,
     Blueprint,
@@ -80,11 +81,22 @@ export async function applyBlueprint({
                 trx,
                 siteId
             );
+        });
+
+        // Push updates to newts/clients only after the transaction has
+        // committed. Doing this while the transaction is still open can
+        // race with the writes (e.g. newts requesting config before the
+        // new targets/resources are actually visible), leaving them out
+        // of sync until manually toggled.
 
         // We need to update the targets on the newts from the successfully updated information
         for (const result of publicResourcesResults) {
             for (const target of result.targetsToUpdate) {
-                    const [site] = await trx
+                // read from the primary: this determines whether/how we push
+                // the just-created target to the newt, so a lagging replica
+                // returning stale or missing data here would silently skip
+                // the push
+                const [site] = await primaryDb
                     .select()
                     .from(sites)
                     .innerJoin(newts, eq(sites.siteId, newts.siteId))
@@ -166,7 +178,6 @@ export async function applyBlueprint({
         logger.debug(
             `Successfully updated private resources for org ${orgId}: ${JSON.stringify(privateResourcesResults)}`
         );
-        });
 
         blueprintSucceeded = true;
         blueprintMessage = "Blueprint applied successfully";