coilyco-flight-deck/eco-replay
1
0
Fork 0
Code Issues 9 Pull requests Projects Releases Packages Wiki Activity Actions

Add coily run-live verb to wrap run-native with SSM token fetch #3

New issue
Open
opened 2026-05-23 20:54:16 +00:00 by coilysiren · 0 comments
coilysiren commented 2026-05-23 20:54:16 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-18T22:32:21Z - https://github.com/coilysiren/eco-replay/issues/6

Problem - Flipping eco-replay from mock to live takes a manual env dance every time: fetch token via coily ops aws ssm get-parameter --name /eco-mcp-app/api-admin-token --with-decryption, export UPSTREAM_URL and UPSTREAM_API_KEY, then coily exec run-native. eco-mcp-app and eco-jobs-tracker have the same shape and the same per-invocation ceremony.

Fix - Add a run-live verb to .coily/coily.yaml that wraps run-native, fetches the token from SSM, and points at http://localhost:3001/api/v1/events. Either:

  1. Per-repo: each repo's coily.yaml declares run-live with the SSM key it cares about.
  2. Hoisted: one verb in coily gaming eco ... (e.g. coily gaming eco run-replay) that knows the standard token + URL.

Option 1 is lower-blast-radius and matches the existing per-repo verb pattern. Option 2 deduplicates if a 4th eco web app shows up.

Adjacent: same gap applies to eco-jobs-tracker and eco-mcp-app. Consider doing the sweep together.

_Originally filed by @coilysiren on 2026-05-18T22:32:21Z - [https://github.com/coilysiren/eco-replay/issues/6](https://github.com/coilysiren/eco-replay/issues/6)_ **Problem** - Flipping eco-replay from mock to live takes a manual env dance every time: fetch token via `coily ops aws ssm get-parameter --name /eco-mcp-app/api-admin-token --with-decryption`, export `UPSTREAM_URL` and `UPSTREAM_API_KEY`, then `coily exec run-native`. eco-mcp-app and eco-jobs-tracker have the same shape and the same per-invocation ceremony. **Fix** - Add a `run-live` verb to `.coily/coily.yaml` that wraps `run-native`, fetches the token from SSM, and points at `http://localhost:3001/api/v1/events`. Either: 1. Per-repo: each repo's `coily.yaml` declares `run-live` with the SSM key it cares about. 2. Hoisted: one verb in `coily gaming eco ...` (e.g. `coily gaming eco run-replay`) that knows the standard token + URL. Option 1 is lower-blast-radius and matches the existing per-repo verb pattern. Option 2 deduplicates if a 4th eco web app shows up. Adjacent: same gap applies to eco-jobs-tracker and eco-mcp-app. Consider doing the sweep together.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/eco-replay#3
No description provided.