gb resolve

Compute the final resolved configuration.

Synopsis

gb resolve [options]

Description

Processes genbox.yaml, resolves $detect markers, applies profile settings, and outputs the final computed configuration. This is what actually gets used when creating environments.

Options

Examples

Basic Resolve

gb resolve

With Profile

gb resolve --profile full-stack

Save to File

gb resolve --output .genbox/resolved.yaml

Resolution Process

1. Load genbox.yaml: Read source configuration
2. Load detected.yaml: Read auto-detected values
3. Apply profile: Merge profile settings
4. Resolve $detect: Replace markers with detected values
5. Compute connections: Determine service URLs
6. Apply defaults: Fill in missing values
7. Validate: Check for errors

Example Output

Resolving configuration...

Loading genbox.yaml... ✓
Loading .genbox/detected.yaml... ✓

Resolving $detect markers:
  apps.web.port: $detect → 3000 (from detected.yaml)
  apps.web.framework: $detect → nextjs (from detected.yaml)
  apps.api.port: 3050 (explicit)
  apps.api.framework: nestjs (explicit)

Resolving connections:
  web → api: will inject NEXT_PUBLIC_API_URL
  api → mongodb: will inject MONGODB_URI
  api → redis: will inject REDIS_URL

Computing environment variables... ✓

Output written to: .genbox/resolved.yaml

Run 'gb validate' to check for errors.

Resolved vs Source

Files Involved

project/
├── genbox.yaml           # Source config (you write this)
└── .genbox/
    ├── detected.yaml     # Auto-detected values
    └── resolved.yaml     # Final computed config

Notes

• gb create runs resolve automatically
• Use for debugging configuration issues
• Resolved config shows exactly what will execute
• Check before creating to catch errors early

See Also

• gb validate - Validate resolved config
• gb config show - View config with explanation
• gb init - Generate initial config