import { type EmulatorCapability, type EmulatorSpec } from "@intentius/chant/op";
export interface FlociAzUpArgs {
    /** Container name. Default: `chant-floci-az`. */
    name?: string;
    /** Host port mapped to the emulator's `:4577`. Default: `4577`. */
    port?: number;
    /** Image. Default: the pinned `floci/floci-az` tag. */
    image?: string;
    /** Readiness timeout in ms. Default: `60000`. */
    timeoutMs?: number;
    /** Health poll interval in ms. Default: `2000`. */
    intervalMs?: number;
}
export interface FlociAzDownArgs {
    /** Container name to remove. Default: `chant-floci-az`. */
    name?: string;
}
export declare const FLOCI_AZ_SPEC: EmulatorSpec;
/**
 * The azure plugin's emulator capability (#1345).
 *
 * The spec below has existed since #746; what was missing was declaring it, so
 * `chant emulator up --all` booted Floci and nothing else even though floci-az
 * was one line away. `AZURE_ENDPOINT_URL` is the var azure's own
 * `describe-resources.ts` and `deep-observe.ts` already read on every live
 * call, which is also what makes `--live --env <local>` reach the emulator
 * instead of real Azure.
 */
export declare const FLOCI_AZ_EMULATOR: EmulatorCapability;
export declare const flociAzExistsCommand: (name: string) => string;
export declare const flociAzRmCommand: (name: string) => string;
export declare const flociAzHealthUrl: (port: number) => string;
/** The ARM endpoint URL (what `azApply`'s `endpoint` should point at). */
export declare const flociAzEndpoint: (port: number) => string;
export declare const flociAzRunCommand: (args?: FlociAzUpArgs) => string;
/** Boot a local floci-az (Azure emulator) in Docker and return its ARM endpoint. */
export declare const flociAzUp: (args?: FlociAzUpArgs, signal?: AbortSignal) => Promise<{
    endpoint: string;
}>;
/** Stop and remove the local floci-az container (no-op if already gone). */
export declare const flociAzDown: (args?: FlociAzDownArgs, signal?: AbortSignal) => Promise<void>;
//# sourceMappingURL=floci-az.d.ts.map