fix: record when modules are activated

Use the activation time to determine which module is the current one.

fixes: 2961

backend/controller/dal/internal/sql/queries.sql

@@ -90,7 +90,7 @@ FROM deployments d
   LEFT JOIN runners r ON d.id = r.deployment_id
 WHERE min_replicas > 0
 GROUP BY d.id, m.name, m.language
-ORDER BY d.created_at;
+ORDER BY d.last_activated_at;
 
 -- name: GetDeploymentsWithMinReplicas :many
 SELECT sqlc.embed(d), m.name AS module_name, m.language
@@ -119,7 +119,7 @@ ORDER BY d.key;
 
 -- name: SetDeploymentDesiredReplicas :exec
 UPDATE deployments
-SET min_replicas = $2
+SET min_replicas = $2, last_activated_at = CASE WHEN min_replicas = 0 THEN (NOW() AT TIME ZONE 'utc') ELSE  last_activated_at END
 WHERE key = sqlc.arg('key')::deployment_key
 RETURNING 1;
 

backend/controller/sql/schema/20241002225509_create_last_activated.sql

@@ -0,0 +1,5 @@
+-- migrate:up
+ALTER TABLE deployments ADD COLUMN last_activated_at TIMESTAMPTZ NOT NULL DEFAULT (NOW() AT TIME ZONE 'utc');
+UPDATE deployments SET last_activated_at = created_at;
+-- migrate:down
+

deployment/base/db-migrate/kustomization.yml

@@ -30,3 +30,4 @@ configMapGenerator:
   - ./schema/20240917062716_change_deployments_index.sql
   - ./schema/20240919001309_create_identity_keys_table.sql
   - ./schema/20240926231955_timeline_async_call_event_types.sql
+  - ./schema/20241002225509_create_last_activated.sql