ObolNetwork / ObolNetwork/obol-stack
Seamless integration between obol-cli and obolup with API key management
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Problem
Currently, launching obolup from obol-cli requires manual steps that break the user flow:
- The obol-stack repository must be cloned separately
- The Gemini API key must be manually placed in the correct .env file path
- Users need to navigate between different directories
- No unified command to go from obol-cli → stack deployment
This creates friction and potential failure points in what should be a seamless stack deployment process.
Current Pain Points
- Repository dependency: Users must manually clone obol-stack repo
- API key management: Gemini API key must be manually configured in specific .env location
- Directory navigation: Users switch between obol-cli and obol-stack directories
- No integration: obol-cli and obolup operate as separate tools without communication
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names obol-cli, obolup, and the obol-stack deployment flow but provides no files or tests. Start by locating the entry points for both tools and tracing the current repository, .env, and Gemini API-key setup. Done should mean a documented unified command can move from obol-cli to stack deployment without manual cloning, directory changes, or key placement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- cli, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100