Module aws_sdk_codeconnections::types

source ·
Expand description

Data structures used by operation inputs/outputs.

Modules§

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

Structs§

  • Connection

    A resource that is used to connect third-party source providers with services like CodePipeline.

  • Host

    A resource that represents the infrastructure where a third-party provider is installed. The host is used when you create connections to an installed third-party provider type, such as GitHub Enterprise Server. You create one host for all connections to that provider.

  • RepositoryLinkInfo

    Information about the repository link resource, such as the repository link ARN, the associated connection ARN, encryption key ARN, and owner ID.

  • RepositorySyncAttempt

    Information about a repository sync attempt for a repository with a sync configuration.

  • RepositorySyncDefinition

    The definition for a repository with a sync configuration.

  • RepositorySyncEvent

    Information about a repository sync event.

  • ResourceSyncAttempt

    Information about a resource sync attempt.

  • ResourceSyncEvent

    Information about a resource sync event for the resource associated with a sync configuration.

  • Revision

    Information about the revision for a specific sync event, such as the branch, owner ID, and name of the repository.

  • SyncBlocker

    Information about a blocker for a sync event.

  • SyncBlockerContext

    The context for a specific sync blocker.

  • SyncBlockerSummary

    A summary for sync blockers.

  • SyncConfiguration

    Information, such as repository, branch, provider, and resource names for a specific sync configuration.

  • Tag

    A tag is a key-value pair that is used to manage the resource.

  • VpcConfiguration

    The VPC configuration provisioned for the host.

Enums§

  • BlockerStatus
    When writing a match expression against BlockerStatus, 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.
  • BlockerType
    When writing a match expression against BlockerType, 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.
  • ConnectionStatus
    When writing a match expression against ConnectionStatus, 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.
  • ProviderType
    When writing a match expression against ProviderType, 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.
  • PublishDeploymentStatus
    When writing a match expression against PublishDeploymentStatus, 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.
  • RepositorySyncStatus
    When writing a match expression against RepositorySyncStatus, 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.
  • ResourceSyncStatus
    When writing a match expression against ResourceSyncStatus, 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.
  • SyncConfigurationType
    When writing a match expression against SyncConfigurationType, 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.
  • TriggerResourceUpdateOn
    When writing a match expression against TriggerResourceUpdateOn, 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.