import { MutagentCore } from "../core.js";
import { RequestOptions } from "../lib/sdks.js";
import { ConnectionError, InvalidRequestError, RequestAbortedError, RequestTimeoutError, UnexpectedClientError } from "../models/errors/http-client-errors.js";
import * as errors from "../models/errors/index.js";
import { MutagentError } from "../models/errors/mutagent-error.js";
import { ResponseValidationError } from "../models/errors/response-validation-error.js";
import { SDKValidationError } from "../models/errors/sdk-validation-error.js";
import * as models from "../models/index.js";
import * as operations from "../models/operations/index.js";
import { APIPromise } from "../types/async.js";
import { Result } from "../types/fp.js";
/**
 * Update provider config
 *
 * @remarks
 * Update an existing provider configuration. When the patch replaces the SECRET — the apiKey field, or the catalog-named secret inside credentialFields — the new credential is connection-tested BEFORE it is written, the same guarantee POST /providers makes on create. A failed test writes nothing: the existing configuration, including fields elsewhere in the same request, is left exactly as it was. Non-secret changes (baseUrl, hostedFamily, apiVersion, other credentialFields entries) are applied without a live probe.
 *
 * If set, this operation will use either {@link Security.apiKey} or {@link Security.bearerAuth} from the global security.
 */
export declare function providerConfigsUpdateProvider(client: MutagentCore, request: operations.UpdateProviderRequest, options?: RequestOptions): APIPromise<Result<models.ProviderConfig, errors.ProviderError | MutagentError | ResponseValidationError | ConnectionError | RequestAbortedError | RequestTimeoutError | InvalidRequestError | UnexpectedClientError | SDKValidationError>>;
//# sourceMappingURL=provider-configs-update-provider.d.ts.map