Function parseFlags

ts/workflow-cli/cli/deploy/index.ts:70–104

(args: string[])

// ---------------------------------------------------------------------------

const USAGE = `Usage: fh-workflow deploy <workflow.json> [flags]

Generates a self-contained, standalone Engine deployment bundle (docker-compose.yml,
engine-config.json, engine.env, README.md). The engine boots the workflow and runs
autonomously. Missing values are filled in interactively, or supplied via
--values when there is no terminal.

LLM provider keys (set one for each provider your Agents use):
${PROVIDER_IDS.map((id) => `  --${providerFlag(id)}-key KEY`).join("\n")}

Custom components (extra containers to run alongside the engine):
  --component DIR                 folder with a component.json (repeatable)

Output:
  --output DIR                    default: ./<workflow-name>-bundle
  --force                         overwrite existing DIR
  --log-level LEVEL               ${logLevelSchema.options.join("|")} (default: info)

Automation (no terminal — e.g. a Claude Code skill or CI):
  --values FILE                   JSON partial deploy config supplying the answers
                                  (chmod 600 — may hold secrets). Without a terminal,
                                  any missing required value exits non-zero.

  --help, -h                      this message
`;

// parseFlags / partialFromFlags / loadValues / missingRequired / configFromPartial
// are exported for unit testing; deployCommand is their only runtime caller.
export function parseFlags(args: string[]): RawFlags {
  // One --<provider>-key string flag per catalog provider (flag = id lowercased).
  const keyOptions = Object.fromEntries(PROVIDER_IDS.map((id) => [`${providerFlag(id)}-key`, { type: "string" as const }]));
  const { values } = parseArgs({
    args,
    options: {
      ...keyOptions,
      output: { type: "string" },
      "log-level": { type: "string" },
      values: { type: "string" },