From 669d118a0f4d0f956dbe0a68633e02dd908af614 Mon Sep 17 00:00:00 2001 From: breis Date: Tue, 28 Jul 2026 13:21:40 -0400 Subject: [PATCH] fix(recipe): set the component token for GG_CONFIG runs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Greengrass recipe's DefaultConfiguration was the one configuration surface without `component.token`. With no token set, the library falls back to the short form of the Greengrass component name, which is reverse-DNS PascalCase — so a GG_CONFIG run published under the PascalCase name while the k8s ConfigMap and every FILE config in this repo already carried the lower-kebab token, and every doc in the repo documents the kebab topics. Set the token explicitly in the recipe, matching the value the other surfaces already use. Purely additive: no other surface changes, and the kebab token was already what non-Greengrass deployments published under. --- recipe.yaml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/recipe.yaml b/recipe.yaml index 7104231..3cf9215 100644 --- a/recipe.yaml +++ b/recipe.yaml @@ -72,6 +72,9 @@ ComponentConfiguration: shop: "test_shop" line: "test_line" component: + # UNS component token. The Greengrass ComponentName is reverse-DNS PascalCase; the token the + # wire carries is lower-kebab, so it is set explicitly rather than derived from the name. + token: telemetry-processor # Cross-route defaults, overlaid by each route (global ⊕ instance). global: defaults: