joelhooks / joelhooks/agent-secrets

feat: Vercel adapter project path configuration

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
109
Forks
7
Avg merge
2h 37m
Merged PRs (30d)
1

Description

Summary

Add project path configuration to the Vercel adapter for cases where vercel env pull needs to run from a specific directory.

Context

File: internal/adapters/vercel/vercel.go:81

// TODO: Consider adding project path configuration

Problem

Currently the Vercel adapter runs vercel env pull from the temp directory. Some Vercel projects may need the command run from the actual project directory to detect the linked project.

Implementation

Option 1: ProjectPath field
type VercelAdapter struct {
    binary      string
    projectPath string  // If set, cd to this path before running vercel
}

func NewWithPath(projectPath string) *VercelAdapter
Option 2: Use vercel --cwd flag
vercel env pull --cwd /path/to/project --environment production
Update .secrets.json
{
  "source": "vercel",
  "project": "my-app",
  "project_path": "/path/to/project",  // optional
  "scope": "production"
}

Acceptance

  • Vercel adapter can run from specified project path
  • Works with linked Vercel projects
  • Backwards compatible (project_path is optional)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at internal/adapters/vercel/vercel.go:81 and inspect how the adapter currently invokes vercel env pull and how .secrets.json fields are parsed. Determine whether the project path should use a field or the --cwd option, then verify the optional setting works for linked projects while existing configurations remain compatible.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.