acme-cli-custom-commands

name	acme-cli-custom-commands
description	How to author custom commands for the acme-cli CLI using the co-generated SDK.

Custom Commands for acme-cli

Overview

The acme-cli CLI supports user-authored custom commands that are compiled into the binary alongside the auto-generated API commands. Custom commands get a fully-wired SDK client that inherits the CLI's auth, retries, TLS, base URL, and global headers — zero configuration required.

Architecture

cli/acme-cli/custom.rs    ← Your command handlers (protected by .fernignore)
cli/acme-cli/sdk.rs       ← Generated bridge: client() + block_on()
cli/acme-cli/main.rs      ← Generated entrypoint (calls custom::register)
acme-cli-sdk/             ← Co-generated typed SDK crate
acme-cli-types/           ← Co-generated typed model crate

Adding a Custom Command

1. Edit cli/acme-cli/custom.rs

This file is protected by .fernignore — fern generate will never overwrite it. Register commands in the register() function:

use acme_cli_sdk::api::*;

pub fn register(app: CliApp) -> CliApp {
    let app = app.command(
        clap::Command::new("my-command")
            .about("Description of your command")
            .arg(clap::Arg::new("id").required(true)),
        |matches, ctx| {
            let id = matches.get_one::<String>("id").unwrap();
            let client = super::sdk::client(ctx);
            let result = super::sdk::block_on(
                client.resource.get(id),
            )?;
            println!("{}", serde_json::to_string_pretty(&result).unwrap());
            Ok(())
        },
    );
    app
}

2. Available SDK Clients

The super::sdk::client(ctx) call returns a acme_cli_sdk::api::Client with the following sub-clients:

(Sub-clients are derived from the API spec at generation time.)

3. Key Patterns

Get the SDK client (execution-sharing, fully authenticated):

let client = super::sdk::client(ctx);

Run an async SDK call from a sync handler:

let result = super::sdk::block_on(
    client.some_resource.some_method(args),
)?;

Use typed models for request/response serialization:

use acme_cli_sdk::api::*;

Regeneration Safety

File	Regenerated?	Notes
cli/acme-cli/custom.rs	No	Protected by .fernignore
cli/acme-cli/sdk.rs	Yes	Bridges AppContext → SDK client
cli/acme-cli/main.rs	Yes	Calls custom::register(app)
acme-cli-sdk/	Yes	Co-generated typed SDK crate
acme-cli-types/	Yes	Co-generated typed models

After running fern generate, your custom.rs is preserved. All generated code (SDK, types, glue, main.rs) is updated to match the latest API spec. If the SDK surface changes (renamed methods, new sub-clients), update your custom.rs to match.

Build & Test

# Build the CLI (includes custom commands)
cargo build

# Run your custom command
acme-cli <your-command> [args]

# Run with verbose output for debugging
RUST_LOG=debug acme-cli <your-command> [args]