ODIN Fleet CLI

> odin fleet servers list
ID Region       City      Server Config        Address        Ports            Created  Status  
21 europe       limburg   Minecraft Production 51.77.85.52    Game Port: 30097 5.7.2024 running 
22 europe       limburg   Minecraft Production 51.77.85.52    Game Port: 30098 5.7.2024 running 
24 northamerica newyork   Minecraft Production 67.220.85.3    Game Port: 30100 5.7.2024 running 
25 asia         singapore Minecraft Production 15.235.216.107 Game Port: 30101 5.7.2024 running 
26 northamerica seattle   Minecraft Production 38.89.70.30    Game Port: 30102 5.7.2024 starting
Please note: Servers in intermediate states (e.g. starting, stopping) are not shown here.
> |

ODIN Fleet provides a simple CLI tool that allows you to interact with ODIN Fleet from your command line. It's written in Deno and uses the TypeScript ODIN Fleet SDK internally.

warning

The CLI tool is still in development, and new features are added regularly. If you have any feedback or feature requests, please let us know. We are also working on a simpler way to install the CLI tool globally.

Installation

Our CLI tool is open-source and available on GitHub. You can clone the repository and build the CLI tool yourself. We are working on providing pre-built binaries for all platforms.

GitHub Repository: https://github.com/4Players/fleet-cli

To install the CLI tool, you need to have Deno installed. You can install Deno by following the instructions on the official Deno website: https://deno.land/. Clone the repo on your workstation and navigate to the project directory.

git clone https://github.com/4Players/fleet-cli.git
cd fleet-cli

Next, run the following command to generate the CLI tool:

deno task build

This will build a odin binary (or odin.exe on Windows) in the root of the project. You can move this binary to a directory in your PATH to use it globally. On macOS and Linux you might need to run the following command to make the binary executable:

chmod +x odin

Development

You need to have npm installed on your system. You can install it by following the instructions on the official npm website: https://www.npmjs.com/get-npm.

If you want to work on the CLI tool, you can need to have openapi-generator-cli installed on your system. You can install it by running the following command:

npm install @openapitools/openapi-generator-cli -g

On Mac you can also use Homebrew to install the openapi-generator-cli.

openapi-generator-cli version-manager set 7.3.0

Updating the underlying SDK

To update the underlying SDK, you need to run the following command to make the script executable (if not done before):

chmod +x generate-sdk.sh

Then run the script to generate the SDK:

./generate-sdk.sh

This will generate the SDK from the OpenAPI specification file. The generated SDK will be placed in the src/api directory. The CLI tool uses this SDK to interact with the ODIN APIs.

Testing the CLI tool

To run the CLI tool in development mode, you can run the following command:

deno run --allow-all src/main.ts

We use --allow-all because the CLI tool needs to access various system resources to work correctly:

• --allow-read to read the configuration file
• --allow-write to write the configuration file
• --allow-net to make API requests
• --allow-env to read environment variables

Building the CLI tool

To build the CLI tool, you can run the following command:

deno task build

Usage

The CLI tool is designed to work in two scenarios:

• You are working in a terminal and can interact with the CLI tool (it will prompt for all missing information)
• You are running the CLI tool in a CI/CD pipeline and need to provide all the necessary information as arguments

Logging in and selecting an application

First, you need to login to the ODIN API. You can do this by running the following command:

odin login

You will be prompted to enter a valid access token. You can get an access token by logging into the dashboard, navigating to the settings section (click on the user profile at the top right and choose Settings from the drop-down menu). You will find the access token in the API section.

Copy an access token that you have generated and paste it into the terminal. The CLI tool will store the access token in a configuration file in your home directory (~/.odin/config.json).

You can also provide the access token as an argument to all commands (this overrides the stored access token and is useful in CI/CD scripts where you cannot prompt the user)

odin fleet images list --accessToken=<access-token>

Next, you need to select an application to work with. You can list all the applications by running the following command:

odin apps list

You will see a list of applications that you have access to. You can select an application by running the following command:

odin apps select

You can also provide an application ID as an argument to all commands (this overrides the selected application and is useful in CI/CD scripts where you cannot prompt the user)

odin fleet images list --appId <application-id>

Working with the CLI tool

The CLI tool is designed to work with the ODIN APIs. You can list, create, update, and delete resources using the CLI tool. The CLI tool is designed to be self-explanatory, and you can get help by running the following command:

odin --help

You can also get help for a specific command by running the following command:

odin fleet --help
odin fleet images --help

Available Resources

The following resources are available in the CLI tool:

• apps - List, select, and create applications
• fleet - Manage ODIN Fleet resources
• fleet images - List, create, update, and delete ODIN Fleet images
• fleet configs - List, create, update, and delete ODIN Fleet server configurations
• fleet deployments - List, create, update, and delete ODIN Fleet deployments
• fleet servers - List, and work with ODIN Fleet servers that have been deployed

Use the --help flag to get more information about each resource and the available commands.

Automation

You can run commands that create, delete or update resources with the --dry-run flag. This will show you the API request that will be made without actually making the request. This is useful to see what the CLI tool will do before actually doing it and it also allows you to copy the API request and run it manually (and slightly modified) if needed. This way you can quickly create scripts for CI/CD. Manually interact with the CLI in --dry-run mode and then use the --payload= flag to run the same command with the payload you want to use.

Example

In this example we will create a new image for the ODIN Fleet. We will first run the command in --dry-run mode to see what the API request will look like:

odin fleet images create --dry-run

The CLI will prompt for various information like the image name, description and which type of image to create. After entering all the information, the CLI will show you the payload that will be sent to the API. You can copy this payload and run the following command:

odin fleet images create --payload='{"name":"my-image","version":"0.4.2","type":"dockerImage",....}}'