import type { HarnessClient } from "../client/harness-client.js";
export interface MaterializeParams {
    pipelineId: string;
    orgId: string;
    projectId: string;
    inputSetIds: string[];
    /**
     * Git context for remote / Git-stored input sets. When omitted, the Harness
     * API resolves the input set from the repo's default branch — which silently
     * returns the wrong values (or 404s) when the set lives on another branch.
     */
    gitContext?: InputSetGitContext;
}
export interface InputSetGitContext {
    branch?: string;
    repoName?: string;
    connectorRef?: string;
    storeType?: string;
}
/** Merge two `pipeline` fragments from input sets (later ids override by variable / stage id). */
export declare function mergeRuntimePipelineFragments(base: Record<string, unknown>, next: Record<string, unknown>): Record<string, unknown>;
/**
 * Returns YAML string `{ pipeline: ... }` suitable for pipeline execute body,
 * or undefined if no ids.
 */
export declare function materializeInputSetsToRuntimeYaml(client: HarnessClient, params: MaterializeParams): Promise<string | undefined>;
//# sourceMappingURL=materialize-input-sets.d.ts.map