From b86c443864c5c306dbb62af95927d633f2963a98 Mon Sep 17 00:00:00 2001
From: Agustin Celentano <12614595+agustincelentano@users.noreply.github.com>
Date: Mon, 3 Aug 2026 11:44:51 -0300
Subject: [PATCH] feat(lambda): declare the scope's available actions in its
 spec
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The list of actions a scope offers lived in the scope_definition module as a
hardcoded default, far from the scope that implements them. That distance is what
let them drift: the default listed "kill-instances" while the containers scope
ships "kill-instance", and the mismatched name resolved to a 404 whose body
reached jq as "404: Not Found" — a parse error that said nothing about a missing
file.

Declaring them here puts the list next to the action templates it names, so
adding or renaming an action is one change in one repository.

The fourteen match the action templates in specs/actions and the specifications
currently registered for this scope.

Requires the module to read the field: nullplatform/tofu-modules#458.
---
 lambda/specs/service-spec.json.tpl | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/lambda/specs/service-spec.json.tpl b/lambda/specs/service-spec.json.tpl
index 3fbdd0c..e5f03c1 100644
--- a/lambda/specs/service-spec.json.tpl
+++ b/lambda/specs/service-spec.json.tpl
@@ -1,4 +1,20 @@
 {
+  "available_actions": [
+    "create-scope",
+    "update-scope",
+    "delete-scope",
+    "start-initial",
+    "start-blue-green",
+    "finalize-blue-green",
+    "switch-traffic",
+    "rollback-deployment",
+    "delete-deployment",
+    "adjust-provisioned-concurrency",
+    "adjust-reserved-concurrency",
+    "invoke",
+    "diagnose-deployment",
+    "diagnose-scope"
+  ],
   "assignable_to": "any",
   "attributes": {
     "schema": {