-
Notifications
You must be signed in to change notification settings - Fork 3
deploy_range.md
Executes ludus range deploy command through the CLI wrapper with optional configuration setting. If a configPath is provided, first runs ludus range config set -f <file> to activate the configuration, then executes ludus range deploy with specified options. Builds command arguments dynamically based on parameters: adds --user for admin operations, --force to bypass prompts, --tags for selective deployment, --limit for pattern matching, --only-roles for specific role deployment, and --verbose-ansible for detailed output. Uses secure command execution with argument arrays to prevent injection. Handles both SSH tunnel and WireGuard VPN connectivity, automatically selecting appropriate connection method. Returns deployment initiation status and raw CLI output for monitoring.
The LLM uses this tool to:
- Deploy ranges after configuration has been set with
set_range_config - Monitor deployment progress and report status
- Handle deployment options like tags, limits, and selective role deployment
- Manage admin operations for deploying other users' ranges
- Provide deployment troubleshooting guidance
Key behaviors:
- Always checks if configuration is set before deploying
- Warns about deployment time (10-45 minutes typically)
- Monitors for credential issues and provides guidance
- Handles force deployments when explicitly requested
- Reports detailed deployment status and any failures
Direct deployment requests:
- "Deploy my range"
- "Start the deployment of my SCCM lab"
- "Deploy the range configuration I just set"
Deployment with options:
- "Deploy my range but only the Windows VMs"
- "Force deploy my range configuration"
- "Deploy my range for user TestUser"
Deployment troubleshooting:
- "Deploy my range with verbose output"
- "Deploy only the domain controller role"
- "Retry the deployment that failed"
Admin operations:
- "Deploy TestUser's range configuration"
- "Force deploy the range for user Bob"