This property MUST be the exact version number of the OpenCLI Specification that this OpenCLI Document uses. The opencli field SHOULD be used by tooling to interpret the OpenCLI Document. This field is not related to the CLI info.version string.

Provides metadata about the CLI. This metadata is used for generating help output and documentation.

The installation methods available for the CLI.

properties that apply to all commands

The commands available for the CLI. Each key should contain the full command starting with the CLI binary name (e.g.: $.info.binary)

The title of the CLI. This will appear in generated help output and documentation.

A short summary of the CLI. This will appear in generated help output and documentation in addition to the description. Markdown may be used for rich text representation.

A longer description of the CLI. This will appear in generated help output and documentation in addition to the summary. Markdown may be used for rich text representation.

Describes the license used by the CLI.

Contact information for the CLI.

The name of the CLI binary. This is the name that will be used to invoke the CLI from the command line.

The version of the OpenCLI Document which typically corresponds to the release version of your CLI.

The name of the license used by the CLI.

The SPDX identifier of the license used by the CLI.

A URL to the license used by the CLI.

The name of the contact person/organization.

The email address of the contact person/organization.

A URL pointing to the contact information.

The name of the installation method.

The command to install the CLI.

A URL pointing to the binary or source code.

The description for the installation method. Markdown may be used for rich text representation.

The list of possible error codes that the CLI can return. Command-specific exit codes can be defined at the command-level.

An object where each property key is a supported file format and each property value is the path to a config file of that format; the defined paths are the expected locations of those config iles. Once defined, alternativeSourced referenced elsewhere in the OpenCLI Spec Document ca use the $FILE type.

A flag for a command.

A short summary of the command. This will appear in generated help output and documentation in addition to the description. Markdown may be used for rich text representation.

A longer description of the command. This will appear in generated help output and documentation in addition to the summary. Markdown may be used for rich text representation.

Alternative names for a given command, e.g. list could be aliases with a shorter version like ls

The positional arguments available for the command. The order in which the arguments are defined is the order in which they should be provided to the command.

The flags available for the command. Flags can be provided in any order.

Determines if the command is hidden from generated help output and documentation. Note that the command is still documented in the OpenCLI document itself and so you should not include anything sensitive. Typically developer helper functions or alternative testing commands may be hidden.

If true, then the command it is a logical grouping of subcommands and is not an executable as a stand-alone command.

The exit code returned by the CLI upon termination to report its execution status.

The name of the argument.

The type of the argument. Codegen tools MAY use this field to coerce argument types before passing them to the command handler implementations.

Indicates if the the argument value is variadic. Multiple values for variadic argumuments can be supplied. A variadic argument must be the last argument declared and only one variadic argument may be declared.

The minimum number of items the variadic argument must receive. Only applicable when variadic is true.

The maximum number of items the variadic argument may receive. Only applicable when variadic is true.

The enumerated choices available for the argument. Codegen tools MAY enforce this enumeration before passing them to the command handler implementations. This will appear in generated help output and documentation. Markdown may be used for rich text representation.

A short summary of the argument. This will appear in generated help output and documentation in addition to the description. Markdown may be used for rich text representation.

A description of the argument. This will appear in generated help output and documentation in addition to the summary. Markdown may be used for rich text representation.

Determines if the argument is mandatory. If required arguments are not supplied, the command will exit in error.

The name of the flag.

The single character short flag.

The type of the flag. Codegen tools WILL use this field to coerce flag types before passing them to the command handler implementations.

Indicates if the the flag value is variadic. Variadic flags can be supplied multiple times. e.g.: --flag value --flag value_two --flag value_three

The minimum number of items the variadic flag must receive. Only applicable when variadic is true.

The maximum number of items the variadic flag may receive. Only applicable when variadic is true.

The enumerated choices available for the flag. If the flag is not one of the choices, the command will exit in error.

A hint to the user about the value of the flag. This will appear in generated help output and documentation.

A short summary of the flag. This will appear in generated help output and documentation in addition to the description. Markdown may be used for rich text representation.

A description of the flag. This will appear in generated help output and documentation in addition to the summary. Markdown may be used for rich text representation.

Determines if the flag is mandatory. If required flags are not supplied, the command will exit in error.

default is the default value the flag will take if it is not provided in the command line. It can be a constant or it can be sourced from the environment or a file. If sourced, resolution will be attempted from each source in the order it is defined, stopping once a value is found or the sources have been exhausted.

The possible sources of the default value; order is important as it determines the order of resolution.

Determines if the flag is hidden from generated help output and documentation.

The name of the source; it can be $ENV indicating the property is sourced from an environment variable OR $FILE, indicating the property is sourced from a config file defined in the global.configFiles section of the document.

The variable name within the environment or JSON path to the property in the config file.

The literal code that is returned by the CLI to the operating system and/or parent process indicating status. Non-zero codes indicate an error.

The enumerated exit code categories. These help the users quickly understand the scope of the error.

A brief, one-line summary of the exit code.

A detailed description of the exit code; can include expected side effects or triage steps.