[01] TERMINAL AUTOMATION

Headless CLI Commands & Automation

Everything the GUI performs is completely scriptable. The portable binary attaches directly to your terminal session, outputs streaming events, and exits with standard exit codes for unattended provisioning, CI runners, and enterprise scripts.

[02] INTERACTIVE EXAMPLES

Common CLI Workflows

1. Batch Tool Installation

Installs individual tools by id. Automatically skips tools already detected on your system.

PowerShell (Install Tools)
PS> .\DevOpsToolsInstaller.exe --install kubectl,terraform,helm [get ] kubectl (kubectl.exe) kubectl: 74% [ok ] kubectl: copied to Tools\bin. It's on your PATH and ready to use. [get ] terraform (terraform_1.9.5_windows_amd64.zip) terraform: 100% (SHA-256 verified) [ok ] terraform: extracted to Tools\terraform and registered in Tools\bin. Done. 2 installed, 1 already present, 0 failed.

2. Provision Curated Stacks

Deploys an entire role-based toolchain with one command (e.g. k8s-starter, devsecops, iac-complete).

PowerShell (Install Bundle)
PS> .\DevOpsToolsInstaller.exe --install-bundle k8s-starter Done. 7 installed, 0 already present, 0 failed.

3. Inventory Status & Markdown Audit Report

Query installed tools and generate an exhaustive markdown diagnostic report for IT onboarding or GitHub issues.

PowerShell (Status & Report)
# Query local tool inventory PS> .\DevOpsToolsInstaller.exe --status # Write markdown audit report of entire workstation PS> .\DevOpsToolsInstaller.exe --report workstation-audit.md

4. Workstation PATH Doctor & Fixer

Inspect user environment variables for dead folders, syntax errors, and duplicate entries, with automatic safe backups before fixing.

PowerShell (PATH Doctor)
# Check User PATH for conflicts PS> .\DevOpsToolsInstaller.exe --path-doctor # Automatically clean, prune missing directories, and deduplicate User PATH PS> .\DevOpsToolsInstaller.exe --fix-path

5. Workstation Profiles & Standalone Bootstrap Script

Export your setup to version-controlled JSON, or generate a standalone script that requires no app binary on the target machine.

PowerShell (Export & Script Gen)
# Export workstation configuration to JSON PS> .\DevOpsToolsInstaller.exe --export-profile team-workstation.json # Restore on a new computer PS> .\DevOpsToolsInstaller.exe --import-profile team-workstation.json # Generate standalone PowerShell script (downloads vendor files with no app dependency) PS> .\DevOpsToolsInstaller.exe --generate-script bootstrap-new-hire.ps1
[03] FLAG SPECIFICATION

Complete CLI Command Reference

All options supported by DevOpsToolsInstaller.exe.

Command Flag Description
--list List every tool in the catalog (ID, name, category, kind).
--status Show which catalog tools are installed, with detected active versions.
--install <id,id,...> Download and install specific tools (skips already-installed).
--install-bundle <bundleId> Install every tool in a curated stack (e.g. k8s-starter, iac-complete).
--update [id,id,...] Update outdated tools; with IDs, force-refresh specific tools.
--uninstall <id,id,...> Uninstall specific tools (removes artifacts, launches vendor uninstallers).
--download-only <id,id,...> Download artifacts without installing (for offline caches / USB drives).
--download-only-bundle <bundleId> Pre-download a curated stack for air-gapped / offline machines.
--export-profile <file> Export installed toolset to a JSON profile.
--import-profile <file> Install tools from a JSON profile (skips already-installed).
--import-winget <file> Migrate packages from a winget export JSON file.
--import-choco <file> Migrate packages from chocolatey list command output.
--report <file> Write an exhaustive markdown workstation report (tools, versions, security).
--generate-script <file> Generate a standalone PowerShell bootstrap script for the current toolset.
--generate-devcontainer <dir> Generate VS Code devcontainer.json and Dockerfile matching workstation tools.
--path-doctor Inspect User PATH for duplicate entries, non-existent directories, and syntax issues.
--fix-path Automatically clean and deduplicate User PATH with a timestamped backup.
--downloads-folder <path> Redirect download directory (e.g. to a USB flash drive) for this execution.
--version Print application version and exit.
--help Display help text and usage flags.
[04] AUTOMATION IN CI & SCRIPTS

Deterministic Exit Codes for Automation

The CLI is built for strict error propagation. Use exit codes in automated setup scripts, Packer image provisioning, or developer bootstrap routines:

EXIT CODES

• 0: All requested operations succeeded cleanly.
• 1: One or more tool downloads or verifications failed.

Vendor setup wizards still launch interactively with standard UAC prompts — nothing bypasses your organization's security policy.

PROVISIONING SNIPPET

PowerShell Error Handling
.\DevOpsToolsInstaller.exe --install-bundle k8s-starter if ($LASTEXITCODE -ne 0) { Write-Error "Workstation provisioning failed!" exit 1 }
[05] GET THE EXECUTABLE

Ready to automate your developer workstation?

Download the standalone portable executable or get it via WinGet.