upgrade_published_schema
async
¶
upgrade_published_schema(
development_schema_arn: Arn,
published_schema_arn: Arn,
minor_version: Version,
*,
config_overrides: Optional[AsyncCloudDirectoryClientConfig] = None,
dry_run: Optional[Bool] = None,
) -> UpgradePublishedSchemaResponse
Upgrades a published schema under a new minor version revision using the current contents of DevelopmentSchemaArn.
Parameters:
-
development_schema_arn(Arn) –The ARN of the development schema with the changes used for the upgrade.
-
published_schema_arn(Arn) –The ARN of the published schema to be upgraded.
-
minor_version(Version) –Identifies the minor version of the published schema that will be created. This parameter is NOT optional.
-
dry_run(Optional[Bool], default:None) –Used for testing whether the Development schema provided is backwards compatible, or not, with the publish schema provided by the user to be upgraded. If schema compatibility fails, an exception would be thrown else the call would succeed. This parameter is optional and defaults to false.
Raises:
-
AccessDeniedException–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.
-
IncompatibleSchemaException–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.
-
InternalServiceException–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.
-
InvalidArnException–Indicates that the provided ARN value is not valid.
-
InvalidAttachmentException–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.
-
LimitExceededException–Indicates that limits are exceeded. See Limits for more information.
-
ResourceNotFoundException–The specified resource could not be found.
-
RetryableConflictException–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.
-
ValidationException–Indicates that your request is malformed in some manner. See the exception message.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_clouddirectory/_services/async_cloud_directory.py
5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 5186 5187 5188 5189 5190 5191 5192 5193 5194 5195 | |