Developer Documentation

List available Configs

Lists all configurations in your account. Configurations define how your images are configured when they are deployed. There are many options available to customize your deployments, such as environment variables, volumes, and ports. It’s easier to manage these configurations using our dashboard, but you can also manage them using the CLI.

Usage

odin fleet configs list [--unused]

Examples

List all configs in a table format:

odin fleet configs list

List the ids of unused configs (useful for cleanup):

odin fleet configs --format="value(id)" --unused

List the configs that match a specific name pattern:

odin fleet configs --format="table(id,name)" --filter="name ~ 'Minecraft*'" 

Flags

  • --unused:
    An optional flag that filters the list to show only images that are not currently in use by any deployments.

  • --filter:
    An optional flag that filters the list of configurations. The filter expression follows a straightforward structure of <field> <operator> <value>. The field can be any property in the dataset, and operators include basic comparison operators such as =, !=, >, <, >=, and <=. Filters can also be combined using logical operators AND, OR, and negated with NOT. You can access nested fields using dot notation, and strings should be enclosed in quotes. Learn more about filters in our filters documentation.

Global Flags

The following flags can be used with any ODIN CLI command:

  • --api-key=<string>
    The API key to use for authentication. If omitted, the CLI will use the api-key stored in the configuration file on your system. Use odin login to store the API key for subsequent commands.

  • --app-id=<string>
    The ID of the app to use for the command. If omitted, the CLI will use the currently selected app. Use odin apps select to select an app interactively.

  • --format=<string>
    The output format to use for the command. Supported formats are json, value, flattened and table. If omitted, the CLI will use the default format specified in the configuration file. Learn more about output formatting.

  • --force
    Forces the command to execute without prompting for confirmation. Use with caution.

  • --quiet
    Suppresses all informational output except for errors. Useful for scripting and automation.