Skip to content

create_schema

create_schema(
    name: SchemaName, *, config_overrides: Optional[CloudDirectoryClientConfig] = None
) -> CreateSchemaResponse

Creates a new schema in a development state. A schema can exist in three phases:

  • Development: This is a mutable phase of the schema. All new schemas are in the development phase. Once the schema is finalized, it can be published.

  • Published: Published schemas are immutable and have a version associated with them.

  • Applied: Applied schemas are mutable in a way that allows you to add new schema facets. You can also add new, nonrequired attributes to existing schema facets. You can apply only published schemas to directories.

Parameters:

  • name (SchemaName) –

    The name that is associated with the schema. This is unique to each account and in each region.

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.

  • 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.

  • LimitExceededException –

    Indicates that limits are exceeded. See Limits for more information.

  • 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.

  • SchemaAlreadyExistsException –

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

  • 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.

Examples:

To create a schema

>>> client.create_schema(name='Customers')
Source code in docs_src/capo_clouddirectory/_services/cloud_directory.py
def create_schema(
    self,
    name: "capo_clouddirectory.types.schema_name.SchemaName",
    *,
    config_overrides: Optional[CloudDirectoryClientConfig] = None,
) -> "capo_clouddirectory.types.create_schema_response.CreateSchemaResponse":
    """<p>Creates a new schema in a development state. A schema can exist in three phases:</p> <ul> <li> <p> <i>Development:</i> This is a mutable phase of the schema. All new schemas are in the development phase. Once the schema is finalized, it can be published.</p> </li> <li> <p> <i>Published:</i> Published schemas are immutable and have a version associated with them.</p> </li> <li> <p> <i>Applied:</i> Applied schemas are mutable in a way that allows you to add new schema facets. You can also add new, nonrequired attributes to existing schema facets. You can apply only published schemas to directories. </p> </li> </ul>

    Args:
        name: <p>The name that is associated with the schema. This is unique to each account and in each region.</p>

    Raises:
        capo_clouddirectory.errors.access_denied_exception.AccessDeniedException: <p>Access denied or directory not found. Either you don't have permissions for this directory or the directory does not exist. Try calling <a>ListDirectories</a> and check your permissions.</p>
        capo_clouddirectory.errors.internal_service_exception.InternalServiceException: <p>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 <a href="http://status.aws.amazon.com/">AWS Service Health Dashboard</a> site to see if there are any operational issues with the service.</p>
        capo_clouddirectory.errors.invalid_arn_exception.InvalidArnException: <p>Indicates that the provided ARN value is not valid.</p>
        capo_clouddirectory.errors.limit_exceeded_exception.LimitExceededException: <p>Indicates that limits are exceeded. See <a href="https://docs.aws.amazon.com/clouddirectory/latest/developerguide/limits.html">Limits</a> for more information.</p>
        capo_clouddirectory.errors.retryable_conflict_exception.RetryableConflictException: <p>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.</p>
        capo_clouddirectory.errors.schema_already_exists_exception.SchemaAlreadyExistsException: <p>Indicates that a schema could not be created due to a naming conflict. Please select a different name and then try again.</p>
        capo_clouddirectory.errors.validation_exception.ValidationException: <p>Indicates that your request is malformed in some manner. See the exception message.</p>
        capo_clouddirectory.errors.UnknownServiceError: The service returned an error code this client does not model.

    Examples:
        To create a schema

        >>> client.create_schema(name='Customers')
    """

    def _handler(
        req: "OperationRequest[capo_clouddirectory.types.create_schema_request.CreateSchemaRequest]",
    ) -> OperationResponse[
        "capo_clouddirectory.types.create_schema_response.CreateSchemaResponse"
    ]:
        import capo_clouddirectory._operations.amazon_cloud_directory_20170111.create_schema

        output, http_response = (
            capo_clouddirectory._operations.amazon_cloud_directory_20170111.create_schema.create_schema(
                req.options, req.input
            )
        )
        return OperationResponse(output=output, response=http_response)

    interceptors_, options_ = self.operation_options(
        config_overrides, OperationLogging("CreateSchema")
    )
    input_: capo_clouddirectory.types.create_schema_request.CreateSchemaRequest = {
        "name": name
    }

    response = execute_pipeline(
        OperationRequest(input=input_, options=options_),
        handler=_handler,
        interceptors=list(interceptors_),
    )
    response.response.close()
    return response.output