You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### TL;DR
Unified server resolution logic across CLI commands by implementing a centralized `get_app_or_config` method.
### What changed?
- Removed the redundant `resolve_server` and `parse_app_identifier` utility functions
- Replaced all instances of these functions with direct calls to `client.get_app_or_config`
- Updated the log tailing functionality to work with server URLs directly
- Simplified server URL resolution in workflow commands
- Enhanced the `tail_logs` command to accept server URLs as input
- Updated help text and examples to reflect the new capabilities
### How to test?
1. Test the logger tail command with different identifier types:
```
mcp-agent cloud logger tail app_abc123 --follow
mcp-agent cloud logger tail apcnf_xyz789 --follow
mcp-agent cloud logger tail https://abc123.mcpcloud.ai --follow
```
2. Test server commands with different identifier types:
```
mcp-agent cloud servers describe app_abc123
mcp-agent cloud servers describe https://abc123.mcpcloud.ai
```
3. Test workflow commands with server URLs:
```
mcp-agent cloud workflows list https://abc123.mcpcloud.ai
```
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- New Features
- Logger tail now supports using a direct server URL in addition to identifiers.
- Refactor
- Unified server resolution across logger, servers, and workflows commands for more consistent behavior.
- Log fetching and streaming now operate directly on server objects, simplifying CLI flows.
- Documentation
- Added an example showing how to tail logs using a server URL.
- Chores
- Removed legacy helper utilities for server parsing/resolution to reduce complexity.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
0 commit comments