Skip to main content

repo-manager

repo-manager is a command-line tool for Cloudaware developer workflows.

Use repo-manager to interact with Cloudaware APIs, manage Compliance Engine v2 repositories, and run the MCP Server locally for MCP-compatible AI tools to query Cloudaware CMDB data through commands such as repo-manager mcp cloudaware.

info
  • Audience: Compliance Engine policy developers, DevOps teams, platform engineers
  • Outcome: repo-manager is installed, available from the command line, and configured to find the required Cloudaware profiles

Requirements​

Before installing repo-manager, make sure Java 17 or later is installed.

Cloudaware recommends using the latest LTS version of Java. If the java or java.exe executable is not available in your PATH, use the full path to the Java executable when running repo-manager commands.

Installation​

repo-manager is distributed as a single JAR file.

Download the latest version:

https://ce.prod.cloudaware.com/repo-manager/repo-manager.jar

After downloading the JAR, you can run it directly with Java or create a command-line alias so repo-manager is available from any directory.

Windows​

  1. Create the .ca directory in your user profile:

    New-Item -ItemType Directory -Force "$env:HOMEDRIVE$env:HOMEPATH\.ca"

  2. Download repo-manager.jar and save it to:

    C:\Users\{username}\.ca\repo-manager.jar

  3. In the same directory, create repo-manager.bat with the following content:

    @echo off
    java -jar "%HOMEDRIVE%%HOMEPATH%\.ca\repo-manager.jar" %*

  4. Add the .ca directory to your user PATH:

    [Environment]::SetEnvironmentVariable("PATH", $env:Path + ";" + $env:HOMEDRIVE + $env:HOMEPATH + "\.ca", "User")

  5. Restart your shell.

After the shell restarts, run repo-manager from any directory.

Linux​

Linux installation instructions are coming soon.

macOS​

macOS installation instructions are coming soon.

Configuration Files​

repo-manager uses the following files and directories:

  • repo-manager.jar - the main executable, usually stored in ~/.ca/repo-manager.jar.
  • repo-manager.json - the tool configuration file, automatically created in the same directory as repo-manager.jar.
  • .ca - the configuration directory where repo-manager looks for files such as profiles.json, which stores API authentication profiles.

When looking for profiles.json, repo-manager checks the following locations in order:

  1. The directory passed with the --config option:

    repo-manager --config=/example/path/my-ca

    In this case, repo-manager uses:

    /example/path/my-ca/profiles.json

  2. The .ca directory inside the repository passed with --repository:

    repo-manager --repository=/example/path/to/repo

    In this case, repo-manager uses:

    /example/path/to/repo/.ca/profiles.json

  3. The .ca directory in the current working directory:

    .ca/profiles.json

  4. The .ca directory in the user home directory:

    ~/.ca/profiles.json

Auto-Update​

repo-manager periodically checks for updates while commands are running. Keeping the tool current helps maintain compatibility with the latest Cloudaware APIs and the latest logic built into repo-manager.

Use the following options to control auto-update behavior:

  • --auto-update - checks for an update immediately. You can use it with another subcommand:

    repo-manager --auto-update docs generate

  • --no-auto-update - suppresses the update check for the current command. Add this option to each command when running multiple commands in sequence.

  • Default behavior - checks for updates when more than 24 hours have passed since the last check.

Help​

To see available commands and options, run:

repo-manager --help

For command details, see CLI Reference.

For release history, see Changelog.

On this page