Skip to content

feat: Support stage names in bridge create -s flag#3

Closed
scubbo wants to merge 1 commit intomainfrom
scubbo/create-s-flag-stages
Closed

feat: Support stage names in bridge create -s flag#3
scubbo wants to merge 1 commit intomainfrom
scubbo/create-s-flag-stages

Conversation

@scubbo
Copy link

@scubbo scubbo commented Mar 14, 2026

Summary

  • The -s/--source flag on bridge create now accepts a stage name (e.g. staging) in addition to filesystem paths
  • When a stage name is detected, bridge shells out to pnpm -w render-staging-overlay <service> to render the Kustomize overlay into plain YAML
  • The rendered manifests are fed into the existing SourceFromManifests pipeline

Test plan

  • Unit tests for isStageSource (distinguishes stage names from file paths)
  • Unit tests for renderStageManifests (validates stage name and service name)
  • Unit tests for PackSingleFile (round-trip pack/unpack)
  • All existing tests pass (go test ./pkg/commands/ ./pkg/archive/)
  • Manual test: bridge create api-feature-flags -s staging from the api repo

The -s/--source flag now accepts a stage name (e.g. "staging") in
addition to filesystem paths. When a stage name is detected, bridge
shells out to `pnpm -w render-staging-overlay <service>` to generate
the manifests, then feeds the rendered YAML into the existing manifest
pipeline.
@scubbo scubbo requested a review from vercel-eddie March 14, 2026 00:51
@scubbo
Copy link
Author

scubbo commented Mar 14, 2026

Closed on the grounds that this is not supposed to have Vercel-specific logic.

@scubbo scubbo closed this Mar 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant