UpdateSchema
Updates the schema name with a new name. Only development schema names can be updated.
Request Syntax
PUT /amazonclouddirectory/2017-01-11/schema/update HTTP/1.1
x-amz-data-partition: SchemaArn
Content-type: application/json
{
"Name": "string
"
}
URI Request Parameters
The request uses the following URI parameters.
- SchemaArn
-
The Amazon Resource Name (ARN) of the development schema. For more information, see Arn Examples.
Required: Yes
Request Body
The request accepts the following data in JSON format.
- Name
-
The name of the schema.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 32.
Pattern:
^[a-zA-Z0-9._-]*$
Required: Yes
Response Syntax
HTTP/1.1 200
Content-type: application/json
{
"SchemaArn": "string"
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- SchemaArn
-
The ARN that is associated with the updated schema. For more information, see Arn Examples.
Type: String
Errors
For information about the errors that are common to all actions, see Common Errors.
- 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.
HTTP Status Code: 403
- 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. HTTP Status Code: 500
- InvalidArnException
-
Indicates that the provided ARN value is not valid.
HTTP Status Code: 400
- LimitExceededException
-
Indicates that limits are exceeded. See Limits for more information.
HTTP Status Code: 400
- ResourceNotFoundException
-
The specified resource could not be found.
HTTP Status Code: 404
- 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.
HTTP Status Code: 409
- SchemaAlreadyExistsException
-
Indicates that a schema could not be created due to a naming conflict. Please select a different name and then try again.
HTTP Status Code: 400
- ValidationException
-
Indicates that your request is malformed in some manner. See the exception message.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: