Skip to content

feat(cli): add --config option to specify custom truss config path #2153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
armishra wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(cli): add --config option to specify custom truss config path #2153

armishra wants to merge 1 commit into from

Conversation

@armishra
Copy link
Contributor

@armishra armishra commented Jan 23, 2026 •
edited
Loading

🚀 What

Add --config option to truss push and truss watch commands to allow specifying a custom config file path instead of the default config.yaml.

💻 How

  • Add optional config_path parameter to TrussSpec, TrussHandle, and load() function
  • Add --config CLI option to push and watch commands
  • Preserve custom config path when reloading config in _update_config()

🔬 Testing

  • CI
  • e2e tests
  • truss push --help & truss watch --help show config options
  • e2e tested different config files in truss push.

🚢 Release requirements

  • Pre-release: None
  • Post-release: None
  • External communication: None

@linear
Copy link

linear bot commented Jan 23, 2026

COR-1000 feat(cli): Add --config option to specify custom truss config file

@armishra @claude
feat(cli): add --config option to specify custom truss config path
6946597 
Add support for specifying a custom config file path via the --config
option in the push and watch commands. This allows users to use
alternative config files instead of the default config.yaml.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@armishra armishra force-pushed the archit/cor-1000-featcli-add-config-option-to-specify-custom-truss-config branch from 1f53ef4 to 6946597 Compare January 23, 2026 23:04
@armishra armishra requested a review from tyranitar January 23, 2026 23:06
@armishra armishra marked this pull request as ready for review January 23, 2026 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@tyranitar tyranitar Awaiting requested review from tyranitar

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@armishra