import { Job } from "../generated/index.js";
export interface MrPlanReportProps {
    /**
     * Lifecycle environment to plan against — the `<environment>` argument of
     * `chant lifecycle plan`.
     */
    environment: string;
    /** Restrict the plan to one lexicon (the optional `[lexicon]` argument). */
    lexicon?: string;
    /** Stage for the plan job. Default: `"plan"` */
    stage?: string;
    /** Image to run chant in. Default: `"node:22-alpine"` */
    image?: string;
    /** Plan against chant-owned resources only (passes `--owned`). */
    ownedOnly?: boolean;
    /** Artifact filename the report is written to. Default: `"tfplan.json"` */
    reportFile?: string;
    /**
     * Commands to run before the plan — typically cloud-credential setup, since
     * the plan queries the live system to classify create/update/delete.
     */
    before?: string[];
    /** Per-member defaults for customizing the generated job. */
    defaults?: {
        plan?: Partial<ConstructorParameters<typeof Job>[0]>;
    };
}
/**
 * A CI job that publishes `chant lifecycle plan` as the GitLab merge-request
 * plan widget.
 *
 * The job runs the plan with `--report gitlab-mr`, writes the count JSON to a
 * file, and declares it as `artifacts:reports:terraform`. GitLab then renders
 * "N to add, M to change, K to delete" on the MR — the same widget Terraform
 * uses. The label reads "Terraform" regardless of producer; that is GitLab's
 * fixed string. Counts are create/update/delete only — `adopt` and `noop` do
 * not appear.
 *
 * The plan reads the live system to classify drift, so wire cloud credentials
 * via `before` or CI variables.
 */
export declare const MrPlanReport: import("@intentius/chant").CompositeDefinition<MrPlanReportProps, {
    plan: import("@intentius/chant").Declarable & Record<string, string>;
}>;
//# sourceMappingURL=mr-plan-report.d.ts.map