import type { MetadataBearer as __MetadataBearer } from "@smithy/types"; import type { UpgradeAppliedSchemaRequest, UpgradeAppliedSchemaResponse } from "../models/models_0"; /** * @public */ export type { __MetadataBearer }; /** * @public * * The input for {@link UpgradeAppliedSchemaCommand}. */ export interface UpgradeAppliedSchemaCommandInput extends UpgradeAppliedSchemaRequest { } /** * @public * * The output of {@link UpgradeAppliedSchemaCommand}. */ export interface UpgradeAppliedSchemaCommandOutput extends UpgradeAppliedSchemaResponse, __MetadataBearer { } declare const UpgradeAppliedSchemaCommand_base: { new (input: UpgradeAppliedSchemaCommandInput): import("@smithy/core/client").CommandImpl; new (input: UpgradeAppliedSchemaCommandInput): import("@smithy/core/client").CommandImpl; getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions; }; /** *

Upgrades a single directory in-place using the PublishedSchemaArn with schema updates found in MinorVersion. Backwards-compatible minor version upgrades are instantaneously available for readers on all objects in the directory. Note: This is a synchronous API call and upgrades only one schema on a given directory per call. To upgrade multiple directories from one schema, you would need to call this API on each directory.

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript * import { CloudDirectoryClient, UpgradeAppliedSchemaCommand } from "@aws-sdk/client-clouddirectory"; // ES Modules import * // const { CloudDirectoryClient, UpgradeAppliedSchemaCommand } = require("@aws-sdk/client-clouddirectory"); // CommonJS import * // import type { CloudDirectoryClientConfig } from "@aws-sdk/client-clouddirectory"; * const config = {}; // type is CloudDirectoryClientConfig * const client = new CloudDirectoryClient(config); * const input = { // UpgradeAppliedSchemaRequest * PublishedSchemaArn: "STRING_VALUE", // required * DirectoryArn: "STRING_VALUE", // required * DryRun: true || false, * }; * const command = new UpgradeAppliedSchemaCommand(input); * const response = await client.send(command); * // { // UpgradeAppliedSchemaResponse * // UpgradedSchemaArn: "STRING_VALUE", * // DirectoryArn: "STRING_VALUE", * // }; * * ``` * * @param UpgradeAppliedSchemaCommandInput - {@link UpgradeAppliedSchemaCommandInput} * @returns {@link UpgradeAppliedSchemaCommandOutput} * @see {@link UpgradeAppliedSchemaCommandInput} for command's `input` shape. * @see {@link UpgradeAppliedSchemaCommandOutput} for command's `response` shape. * @see {@link CloudDirectoryClientResolvedConfig | config} for CloudDirectoryClient's `config` shape. * * @throws {@link AccessDeniedException} (client fault) *

Access denied or directory not found. Either you don't have permissions for this directory or the directory does not exist. Try calling ListDirectories and check your permissions.

* * @throws {@link IncompatibleSchemaException} (client fault) *

Indicates a failure occurred while performing a check for backward compatibility between the specified schema and the schema that is currently applied to the directory.

* * @throws {@link InternalServiceException} (server fault) *

Indicates a problem that must be resolved by Amazon Web Services. This might be a transient error in which case you can retry your request until it succeeds. Otherwise, go to the AWS Service Health Dashboard site to see if there are any operational issues with the service.

* * @throws {@link InvalidArnException} (client fault) *

Indicates that the provided ARN value is not valid.

* * @throws {@link InvalidAttachmentException} (client fault) *

Indicates that an attempt to make an attachment was invalid. For example, attaching two nodes * with a link type that is not applicable to the nodes or attempting to apply a schema to a directory a second time.

* * @throws {@link ResourceNotFoundException} (client fault) *

The specified resource could not be found.

* * @throws {@link RetryableConflictException} (client fault) *

Occurs when a conflict with a previous successful write is detected. For example, if a write operation occurs on an object and then an attempt is made to read the object using “SERIALIZABLE” consistency, this exception may result. This generally occurs when the previous write did not have time to propagate to the host serving the current request. A retry (with appropriate backoff logic) is the recommended response to this exception.

* * @throws {@link SchemaAlreadyExistsException} (client fault) *

Indicates that a schema could not be created due to a naming conflict. Please select a * different name and then try again.

* * @throws {@link ValidationException} (client fault) *

Indicates that your request is malformed in some manner. See the exception * message.

* * @throws {@link CloudDirectoryServiceException} *

Base exception class for all service exceptions from CloudDirectory service.

* * * @public */ export declare class UpgradeAppliedSchemaCommand extends UpgradeAppliedSchemaCommand_base { /** @internal type navigation helper, not in runtime. */ protected static __types: { api: { input: UpgradeAppliedSchemaRequest; output: UpgradeAppliedSchemaResponse; }; sdk: { input: UpgradeAppliedSchemaCommandInput; output: UpgradeAppliedSchemaCommandOutput; }; }; }