Configuration & Utilities

This page covers the utility commands that support the deployment workflow: configuration management, manifest validation, manifest loading, and version checking.

config

Manage CLI configuration stored at ~/.openmcf/config.yaml.

config set

Set a configuration value.

openmcf config set backend-url https://api.example.com

Available keys:

config get

Retrieve a configuration value.

openmcf config get backend-url

Prints the value to stdout. Exits with code 1 if the key is not set.

config list

List all configuration values.

openmcf config list

Prints all set configuration values in key=value format. If no values are set, prints "No configuration values set".

validate-manifest

Validate a manifest against its Protocol Buffer schema without deploying. This runs the same validation that deployment commands perform before execution, allowing you to catch errors early.

Aliases: validate

openmcf validate -f database.yaml
openmcf validate database.yaml                                # positional arg
openmcf validate --clipboard                                  # from clipboard
openmcf validate --kustomize-dir services/api --overlay prod  # from kustomize

The command accepts a manifest from any source: file path (as a flag or positional argument), clipboard, or kustomize build. See Manifest Source Flags in the CLI Reference for all input options.

Validation checks the manifest against the component's protobuf schema using protovalidate. This catches:

• Missing required fields
• Invalid field values (wrong types, out-of-range values)
• Constraint violations defined in buf.validate annotations
• Unrecognized apiVersion or kind

On success, prints a confirmation message and exits with code 0. On failure, prints detailed validation errors and exits with code 1.

load-manifest

Load a manifest, apply defaults and overrides, and print the resolved result. This is useful for inspecting what the CLI will actually see after all processing is applied.

Aliases: load

openmcf load -f database.yaml
openmcf load database.yaml                                    # positional arg
openmcf load --clipboard                                      # from clipboard
openmcf load -f api.yaml --set spec.container.replicas=5      # with overrides
openmcf load --kustomize-dir services/api --overlay prod      # from kustomize

The command:

1. Resolves the manifest from the specified source
2. Applies --set overrides if provided
3. Fills in protobuf default values
4. Prints the fully resolved manifest as YAML to stdout

This is the same processing pipeline that deployment commands use before handing off to the IaC engine. Use it to verify that your overrides, kustomize builds, and manifest sources produce the expected result.

Flags

Accepts all manifest source flags (-f, -c, -i, --kustomize-dir, --overlay) plus:

Manifest Source Resolution

Both validate-manifest and load-manifest use the same manifest resolution logic as deployment commands. When multiple source flags are provided, the CLI uses the first match in priority order:

A positional argument (e.g., openmcf validate database.yaml) is also accepted for backward compatibility. When a positional argument is provided, it takes precedence over all flags.

URL manifests (paths starting with http:// or https://) are downloaded to ~/.openmcf/downloads/ and cached locally.

version

Display the current CLI version and check for available updates.

openmcf version
openmcf -v
openmcf --version

The command prints the current version, fetches the latest available version from GitHub releases, and indicates whether an update is available. If a newer version exists, it suggests running openmcf upgrade.

What's Next

• CLI Reference — Complete flag reference for all commands
• Module Management — Module versioning, staging area, and CLI upgrades
• Unified Commands — Provisioner-agnostic deployment commands