interface ValidateSourceOptions {
    /** Index of the source to validate, in `PipelineFormData.sources`. */
    sourceIndex: number;
    validateCdc?: boolean;
}
/**
 * Validates a single source against the RDI server.
 *
 * Unlike `useUpdatePipelineWithFormData` (a full-pipeline `PUT`) this sends a
 * `PATCH` carrying only the source under test, so sources the user has not
 * configured yet are never submitted and never fail validation. Merge-patch
 * semantics leave every other section of the stored config untouched, which is
 * also why no `active` or `metadata` is sent.
 *
 * The payload also carries the pipeline-level sections the Settings step owns —
 * `processors` (including `target_data_type`) and `targets`. The Settings step
 * itself only saves a draft: persisting from there needs the target's secrets
 * mounted, which fails while the workspace is still deploying. This PATCH is
 * the wizard's first server write and already runs against a live RDI, so the
 * settings ride along with it. The values are pipeline-wide, so re-sending them
 * on every source test is an idempotent no-op.
 */
export declare const useValidateSourceWithFormData: () => {
    validateSource: ({ sourceIndex, validateCdc }: ValidateSourceOptions) => Promise<import("../../sdk/pipeline/types").PipelineOperationResponse>;
    isPending: boolean;
    error: Error | null;
};
export {};