From 2ecc6029632024ff8b7ead18f0436641d3520236 Mon Sep 17 00:00:00 2001 From: nathan Date: Tue, 2 Jun 2026 12:15:25 -0400 Subject: [PATCH] remove chat artifacts --- documentation/plans/plan-autoDeployEnrichment.md | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/documentation/plans/plan-autoDeployEnrichment.md b/documentation/plans/plan-autoDeployEnrichment.md index 03eebb5..aeef91a 100644 --- a/documentation/plans/plan-autoDeployEnrichment.md +++ b/documentation/plans/plan-autoDeployEnrichment.md @@ -1,11 +1,3 @@ -This is actually better than Option C as originally conceived. Komodo has a proper API client with a `DeployStack` execute endpoint — meaning the workflow doesn't need to construct webhook URLs at all. It can just call the Komodo API directly by stack name. - -There's even a GitHub Marketplace action (`komodoactions`) that wraps this exact pattern — API key + secret + stack name → deploy. That's compatible with Gitea Actions. - -Here's the plan document to commit before the Claude Code session: - ---- - **`documentation/plans/plan-autoDeployEnrichment.md`** ```markdown @@ -127,8 +119,4 @@ Reflect the new secret names in the Auto-Deploy section. 2. Komodo service user created with Stack Execute permissions 3. API key + secret copied and ready to add as Gitea secrets 4. Confirm stack names in homelab repo match stack names in Komodo UI -``` - ---- - -Commit that to `documentation/plans/plan-autoDeployEnrichment.md` and you're ready for the next session. The runner setup is still the blocker — nothing else can be tested until that's in place. \ No newline at end of file +``` \ No newline at end of file