Uh oh!
There was an error while loading. Please reload this page.
Align api cli, and mcp - #278
Conversation
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This PR is targeting If this is a regular feature/fix PR, please change the base branch to Current base: |
This PR is targeting If this is a regular feature/fix PR, please change the base branch to Current base: |
The Tower API scopes apps to environments but the CLI and MCP tools were not fully exposing this. This commit: - Adds --environment/-e flag to `tower apps list` and `tower apps show` (defaulting to "default") - Adds environment parameter to MCP tools: tower_deploy, tower_apps_list, tower_apps_show, and tower_run_remote - Adds new MCP tools: tower_catalogs_list and tower_catalogs_show - Includes CLI arg parsing tests for the new flags Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This PR is targeting If this is a regular feature/fix PR, please change the base branch to Current base: |
The API returns all apps when environment is omitted, and only filters when explicitly provided. Updated list_apps to take Option<&str> so the default behavior shows all apps across environments. The environment param is still available for explicit filtering. Also added version field to MCP apps list output. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
bradhe
left a comment
There was a problem hiding this comment.
Generally looks good to me!
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Context:
The API scopes apps, catalogs and secrets to environments, and the CLI
tower deploycommand already supports --environment / -e (defaulting to "default"). However:Specifically, the shortcomings on the MCP don't allow for critical use cases (deploy apps to specific environments, run apps in specific environments, etc.)
Note: The secrets MCP tools (tower_secrets_list, tower_secrets_create, tower_secrets_delete) already correctly handle environments. There are no
catalog MCP tools currently, and the CLI catalogs list already supports --environment.
The desired behavior: