@lotiai/composer 0.2.4 → 0.2.5

package/dist/internal/async/register-scripts/sync-schedules-cli.js

@@ -9,7 +9,7 @@ exports.runSyncSchedulesCli = runSyncSchedulesCli;
  *
  * Framework helper that implements the complete command-line entrypoint for
  * a composer-instance's `sync-schedules` script. Each composer instance
- * (interchange, josu, etc.) needs exactly one thin wrapper that:
+ * needs exactly one thin wrapper that:
  *
  * ```typescript
  * import { isScheduleDefinition, runSyncSchedulesCli } from "@lotiai/composer";
@@ -51,9 +51,9 @@ const sync_schedules_1 = require("./sync-schedules");
 const sync_schedules_via_lambda_1 = require("./sync-schedules-via-lambda");
 /**
  * Builds the default schedule-sync Lambda function name for the current
- * environment. Mirrors `createResourceName(taggingConfig,
- * "temporal-schedule-sync")` in `infrastructure/shared`: `loti-ic` prefix +
- * environment + resource slug with hyphens stripped.
+ * environment: an infra resource prefix + environment + resource slug with
+ * hyphens stripped. Must match the name the schedule-sync Lambda is deployed
+ * under; override with `--lambda` if your deployment uses a different name.
  */
 function defaultLambdaFunctionName(environment) {
     return `loti-ic-${environment}-temporalschedulesync`;

package/dist/internal/async/register-scripts/sync-schedules-via-lambda.d.ts

@@ -11,7 +11,7 @@ export interface SyncSchedulesViaLambdaOptions {
     schedules: ScheduleDefinition[];
     /**
      * Name of the schedule-sync Lambda to invoke (e.g.
-     * `"loti-ic-prod-temporalschedulesync"`).
+     * `"my-schedule-sync-function"`).
      *
      * Ignored in `"emit"` mode but still required for type-safety.
      */

package/dist/internal/async/register-scripts/sync-schedules-via-lambda.js

@@ -11,7 +11,7 @@ exports.syncSchedulesViaLambda = syncSchedulesViaLambda;
  *
  * This is the intended deploy-time path: CI assumes an AWS role with
  * `lambda:InvokeFunction` permission and runs this helper from a
- * composer-instance script (e.g. `@loti/composer-ix` `sync-schedules`).
+ * composer-instance's `sync-schedules` script.
  *
  * Supports two modes:
  * - `"invoke"` (default): invokes the Lambda synchronously, logs tail logs
@@ -30,7 +30,7 @@ exports.syncSchedulesViaLambda = syncSchedulesViaLambda;
  *
  * await syncSchedulesViaLambda(composer, {
  *   schedules: Object.values(schedules).filter(isScheduleDefinition),
- *   lambdaFunctionName: "loti-ic-prod-temporalschedulesync",
+ *   lambdaFunctionName: "my-schedule-sync-function",
  * });
  * ```
  *

package/docker-compose.temporal.yml

@@ -9,7 +9,7 @@
 
 services:
   postgresql:
-    image: postgres:14
+    image: postgres:17
     container_name: temporal-postgresql
     environment:
       POSTGRES_USER: temporal
@@ -20,7 +20,13 @@ services:
       # talk to postgresql:5432 over the Docker network.
       - "${TEMPORAL_DB_PORT:-5432}:5432"
     volumes:
-      - postgres-data:/var/lib/postgresql/data
+      # The volume name is pinned to the Postgres major version. A major bump
+      # (e.g. 14 -> 17) therefore renames it, so Compose provisions a fresh
+      # volume instead of mounting an older major's data directory into the new
+      # server -- Postgres refuses to start on a data dir from a previous major.
+      # The old volume is left orphaned (harmless; `docker volume prune` clears
+      # it). This is throwaway local Temporal metadata, so a reset is expected.
+      - temporal-postgres17-data:/var/lib/postgresql/data
     networks:
       - temporal-network
     healthcheck:
@@ -109,13 +115,18 @@ services:
           sleep 2
         done
 
-        # Keep local namespaces aligned with the canonical shared constants.
-        for namespace in interchange outpost josu; do
-          if temporal operator namespace describe -n "$namespace" --address temporal:7233 >/dev/null 2>&1; then
-            echo "Temporal namespace '$namespace' already exists."
+        # Namespaces to ensure exist. Defaults to a single "default" namespace;
+        # override TEMPORAL_NAMESPACES with a space-separated list (Docker
+        # Compose interpolates it from the host environment at parse time).
+        # The loop variable below is written with a doubled dollar sign so
+        # Compose passes it through to the shell literally instead of
+        # interpolating it to an empty string.
+        for namespace in ${TEMPORAL_NAMESPACES:-default}; do
+          if temporal operator namespace describe -n "$$namespace" --address temporal:7233 >/dev/null 2>&1; then
+            echo "Temporal namespace '$$namespace' already exists."
           else
-            temporal operator namespace create -n "$namespace" --retention 90d --address temporal:7233
-            echo "Temporal namespace '$namespace' created."
+            temporal operator namespace create -n "$$namespace" --retention 90d --address temporal:7233
+            echo "Temporal namespace '$$namespace' created."
           fi
         done
     networks:
@@ -136,7 +147,7 @@ services:
       - temporal-network
 
 volumes:
-  postgres-data:
+  temporal-postgres17-data:
     driver: local
 
 networks:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotiai/composer",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "A framework for building type-safe, DAG-based workflows with optional Temporal integration.",
   "license": "MIT",
   "keywords": [