#[non_exhaustive]
pub enum UpdateDocumentErrorKind {
DocumentVersionLimitExceeded(DocumentVersionLimitExceeded),
DuplicateDocumentContent(DuplicateDocumentContent),
DuplicateDocumentVersionName(DuplicateDocumentVersionName),
InternalServerError(InternalServerError),
InvalidDocument(InvalidDocument),
InvalidDocumentContent(InvalidDocumentContent),
InvalidDocumentOperation(InvalidDocumentOperation),
InvalidDocumentSchemaVersion(InvalidDocumentSchemaVersion),
InvalidDocumentVersion(InvalidDocumentVersion),
MaxDocumentSizeExceeded(MaxDocumentSizeExceeded),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the UpdateDocument
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
DocumentVersionLimitExceeded(DocumentVersionLimitExceeded)
The document has too many versions. Delete one or more document versions and try again.
DuplicateDocumentContent(DuplicateDocumentContent)
The content of the association document matches another document. Change the content of the document and try again.
DuplicateDocumentVersionName(DuplicateDocumentVersionName)
The version name has already been used in this document. Specify a different version name, and then try again.
InternalServerError(InternalServerError)
An error occurred on the server side.
InvalidDocument(InvalidDocument)
The specified SSM document doesn't exist.
InvalidDocumentContent(InvalidDocumentContent)
The content for the document isn't valid.
InvalidDocumentOperation(InvalidDocumentOperation)
You attempted to delete a document while it is still shared. You must stop sharing the document before you can delete it.
InvalidDocumentSchemaVersion(InvalidDocumentSchemaVersion)
The version of the document schema isn't supported.
InvalidDocumentVersion(InvalidDocumentVersion)
The document version isn't valid or doesn't exist.
MaxDocumentSizeExceeded(MaxDocumentSizeExceeded)
The size limit of a document is 64 KB.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext
, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source
for more details about the underlying cause.