nathan/homelab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Releases Wiki Activity

remove chat artifacts
Some checks failed
Auto-Deploy Changed Stacks / deploy (push) Failing after 4s
Details

Browse Source
This commit is contained in:
nathan 2026-06-02 12:15:25 -04:00
parent 1545d7fd2e
commit 2ecc602963
1 changed files with 1 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
documentation/plans/plan-autoDeployEnrichment.md
View File

@ -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
@ -128,7 +120,3 @@ Reflect the new secret names in the Auto-Deploy section.
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.