Module aws_sdk_codecatalyst::types 
source · Expand description
Data structures used by operation inputs/outputs.
Modules
- Builders
- Error types that Amazon CodeCatalyst can respond with.
Structs
- Information about a specified personal access token (PAT). 
- Information about connection details for a Dev Environment. 
- Information about the source repsitory for a Dev Environment. 
- Information about the configuration of a Dev Environment session. 
- Information about a Dev Environment. 
- Information about an email address. 
- Information about an entry in an event log of Amazon CodeCatalyst activity. 
- Information about the payload of an event recording Amazon CodeCatalyst activity. 
- Information about the commands that will be run on a Dev Environment when an SSH session begins. 
- Information about an integrated development environment (IDE) used in a Dev Environment. 
- Information about the configuration of an integrated development environment (IDE) for a Dev Environment. 
- Information about a source repository returned in a list of source repositories. 
- Information about a branch of a source repository returned in a list of branches. 
- Information about the persistent storage for a Dev Environment. 
- Information about the configuration of persistent storage for a Dev Environment. 
- Information about a project in a space. 
- nformation about the filter used to narrow the results returned in a list of projects. 
- Information about a project. 
- Information about a repository that will be cloned to a Dev Environment. 
- Information about an space. 
- Information about a user whose activity is recorded in an event for a space. 
Enums
- When writing a match expression againstCatalogActionVersionFileRecordType, 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.
- When writing a match expression againstComparisonOperator, 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.
- When writing a match expression againstDevEnvironmentSessionType, 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.
- When writing a match expression againstDevEnvironmentStatus, 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.
- When writing a match expression againstFilterKey, 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.
- When writing a match expression againstInstanceType, 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.
- When writing a match expression againstOperationType, 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.
- When writing a match expression againstUserType, 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.