Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Account
Settings Proton settings that are used for multiple services in the Amazon Web Services account.
- Compatible
Environment Template Compatible environment template data.
- Compatible
Environment Template Input Compatible environment template data.
- Component
Detailed data of an Proton component resource.
For more information about components, see Proton components in the Proton User Guide.
- Component
State The detailed data about the current state of the component.
- Component
Summary Summary data of an Proton component resource.
For more information about components, see Proton components in the Proton User Guide.
- Counts
Summary Summary counts of each Proton resource type.
- Deployment
The detailed information about a deployment.
- Deployment
Summary Summary data of the deployment.
- Environment
Detailed data of an Proton environment resource. An Proton environment is a set of resources shared across Proton services.
- Environment
Account Connection Detailed data of an Proton environment account connection resource.
- Environment
Account Connection Summary Summary data of an Proton environment account connection resource.
- Environment
State The detailed data about the current state of the environment.
- Environment
Summary Summary data of an Proton environment resource. An Proton environment is a set of resources shared across Proton services.
- Environment
Template The environment template data.
- Environment
Template Filter A search filter for environment templates.
- Environment
Template Summary The environment template data.
- Environment
Template Version The environment template version data.
- Environment
Template Version Summary A summary of the version of an environment template detail data.
- List
Service Instances Filter A filtering criterion to scope down the result list of the
ListServiceInstances
action.- Output
An infrastructure as code defined resource output.
- Provisioned
Resource Detail data for a provisioned resource.
- Repository
Detailed data of a linked repository—a repository that has been registered with Proton.
- Repository
Branch Detail data for a linked repository branch.
- Repository
Branch Input Detail input data for a linked repository branch.
- Repository
Summary Summary data of a linked repository—a repository that has been registered with Proton.
- Repository
Sync Attempt Detail data for a repository sync attempt activated by a push to a repository.
- Repository
Sync Definition A repository sync definition.
- Repository
Sync Event Repository sync event detail data for a sync attempt.
- Resource
Counts Summary Summary counts of each Proton resource types.
- Resource
Sync Attempt Detail data for a resource sync attempt activated by a push to a repository.
- Resource
Sync Event Detail data for a resource sync event.
- Revision
Revision detail data for a commit and push that activates a sync attempt
- S3Object
Source Template bundle S3 bucket data.
- Service
Detailed data of an Proton service resource.
- Service
Instance Detailed data of an Proton service instance resource.
- Service
Instance State The detailed data about the current state of this service instance.
- Service
Instance Summary Summary data of an Proton service instance resource.
- Service
Pipeline Detailed data of an Proton service instance pipeline resource.
- Service
Pipeline State The detailed data about the current state of the service pipeline.
- Service
Summary Summary data of an Proton service resource.
- Service
Sync Blocker Summary If a service instance is manually updated, Proton wants to prevent accidentally overriding a manual change.
A blocker is created because of the manual update or deletion of a service instance. The summary describes the blocker as being active or resolved.
- Service
Sync Config Detailed data of the service sync configuration.
- Service
Template Detailed data of an Proton service template resource.
- Service
Template Summary Summary data of an Proton service template resource.
- Service
Template Version Detailed data of an Proton service template version resource.
- Service
Template Version Summary Summary data of an Proton service template version resource.
- Sync
Blocker Detailed data of the sync blocker.
- Sync
Blocker Context Detailed data of the context of the sync blocker.
- Tag
A description of a resource tag.
- Template
Sync Config The detail data for a template sync configuration.
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. - Component
Deployment Update Type - When writing a match expression against
ComponentDeploymentUpdateType
, 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. - Deployment
State The detailed data about the current state of the deployment.
- Deployment
Status - When writing a match expression against
DeploymentStatus
, 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. - Deployment
Target Resource Type - When writing a match expression against
DeploymentTargetResourceType
, 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. - Deployment
Update Type - When writing a match expression against
DeploymentUpdateType
, 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. - Environment
Account Connection Requester Account Type - When writing a match expression against
EnvironmentAccountConnectionRequesterAccountType
, 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. - Environment
Account Connection Status - When writing a match expression against
EnvironmentAccountConnectionStatus
, 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. - List
Service Instances Filter By - When writing a match expression against
ListServiceInstancesFilterBy
, 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. - List
Service Instances Sort By - When writing a match expression against
ListServiceInstancesSortBy
, 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. - Provisioned
Resource Engine - When writing a match expression against
ProvisionedResourceEngine
, 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. - Provisioning
- When writing a match expression against
Provisioning
, 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
Provider - When writing a match expression against
RepositoryProvider
, 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
Deployment Status - When writing a match expression against
ResourceDeploymentStatus
, 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. - Service
Status - When writing a match expression against
ServiceStatus
, 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. - Service
Template Supported Component Source Type - When writing a match expression against
ServiceTemplateSupportedComponentSourceType
, 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. - Sort
Order - When writing a match expression against
SortOrder
, 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
Type - When writing a match expression against
SyncType
, 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. - Template
Type - When writing a match expression against
TemplateType
, 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. - Template
Version Source Input Template version source data.
- Template
Version Status - When writing a match expression against
TemplateVersionStatus
, 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.