Module aws_sdk_amplify::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS Amplify can respond with.

Structs

• App

  Represents the different branches of a repository for building, deploying, and hosting an Amplify app.

• Artifact

  Describes an artifact.

• AutoBranchCreationConfig

  Describes the automated branch creation configuration.

• Backend

  Describes the backend properties associated with an Amplify Branch.

• BackendEnvironment

  Describes the backend environment for an Amplify app.

• Branch

  The branch for an Amplify app, which maps to a third-party repository branch.

• CustomRule

  Describes a custom rewrite or redirect rule.

• DomainAssociation

  Describes a domain association that associates a custom domain with an Amplify app.

• Job

  Describes an execution job for an Amplify app.

• JobSummary

  Describes the summary for an execution job for an Amplify app.

• ProductionBranch

  Describes the information about a production branch for an Amplify app.

• Step

  Describes an execution step, for an execution job, for an Amplify app.

• SubDomain

  The subdomain for the domain association.

• SubDomainSetting

  Describes the settings for the subdomain.

• Webhook

  Describes a webhook that connects repository events to an Amplify app.

Enums

• DomainStatus
  When writing a match expression against DomainStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• JobStatus
  When writing a match expression against JobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• JobType
  When writing a match expression against JobType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Platform
  When writing a match expression against Platform, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RepositoryCloneMethod
  When writing a match expression against RepositoryCloneMethod, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Stage
  When writing a match expression against Stage, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.