Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Connection
A resource that is used to connect third-party source providers with services like CodePipeline.
Note: A connection created through CloudFormation, the CLI, or the SDK is in `PENDING` status by default. You can make its status `AVAILABLE` by updating the connection in the console.
- 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.
A host created through the CLI or the SDK is in `PENDING` status by default. You can make its status `AVAILABLE` by setting up the host in the console.
- Repository
Link Info Information about the repository link resource, such as the repository link ARN, the associated connection ARN, encryption key ARN, and owner ID.
- Repository
Sync Attempt Information about a repository sync attempt for a repository with a sync configuration.
- Repository
Sync Definition The definition for a repository with a sync configuration.
- Repository
Sync Event Information about a repository sync event.
- Resource
Sync Attempt Information about a resource sync attempt.
- Resource
Sync Event 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.
- Sync
Blocker Information about a blocker for a sync event.
- Sync
Blocker Context The context for a specific sync blocker.
- Sync
Blocker Summary A summary for sync blockers.
- Sync
Configuration 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.
This tag is available for use by Amazon Web Services services that support tags.
- VpcConfiguration
The VPC configuration provisioned for the host.
Enums§
- Blocker
Status - 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. - Blocker
Type - 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. - Connection
Status - 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. - Provider
Type - 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. - Publish
Deployment Status - 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. - Pull
Request Comment - When writing a match expression against
PullRequestComment
, 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. - Repository
Sync Status - 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. - Resource
Sync Status - 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. - Sync
Configuration Type - 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. - Trigger
Resource Update On - 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.