import { APICommand } from '../index.js'; /** * `qfg run` — resolve Quonfig configs into env vars and exec a child process. * * Use this for tools that read env vars at module import (drizzle-kit migrate, * next-auth's AUTH_SECRET, build steps, one-shot scripts) where going through * `instrumentation.ts` / SDK init isn't possible. * * The flag separator `--` is REQUIRED between `qfg run` flags and the child * command. Flags that look like child flags (e.g. `--silent`) without `--` * would otherwise be eaten by oclif. * * Auth/env mode is binary — see resolve-run-environment.ts for the full rule. */ export default class Run extends APICommand { static args: { command: import("@oclif/core/lib/interfaces/parser.js").Arg>; }; static description: string; static examples: string[]; static flags: { env: import("@oclif/core/lib/interfaces/parser.js").OptionFlag; 'env-file': import("@oclif/core/lib/interfaces/parser.js").OptionFlag; environment: import("@oclif/core/lib/interfaces/parser.js").OptionFlag; 'preserve-env': import("@oclif/core/lib/interfaces/parser.js").BooleanFlag; }; static strict: boolean; /** * Override APICommand.init() — that base eagerly calls getClient(), which * walks the OAuth path and fails before we've even validated the mode rule. * For `qfg run` in Mode A (SDK key), we never need a JWT at all; for Mode B * we'll mint the client on demand from run(). */ init(): Promise; run(): Promise; private execChild; /** * Resolve a single RawConfigWithDependencies into a stringified env value. * Mirrors the providedBy / decryptWith handling in commands/get.ts so the * two paths agree on what "the value of this key on the CLI host" means. */ private resolveOne; private resolveValues; private resolveViaSdkKey; private resolveViaUserAuth; }