Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- DbCluster
Summary Describes a summary of a Timestream for InfluxDB cluster.
- DbInstance
ForCluster Summary Contains a summary of a DB instance belonging to a DB cluster.
- DbInstance
Summary Contains a summary of a DB instance.
- DbParameter
Group Summary Contains a summary of a DB parameter group.
- Duration
Duration for InfluxDB parameters in Timestream for InfluxDB.
- InfluxD
Bv2Parameters All the customer-modifiable InfluxDB v2 parameters in Timestream for InfluxDB.
- InfluxD
Bv3Core Parameters All the customer-modifiable InfluxDB v3 Core parameters in Timestream for InfluxDB.
- InfluxD
Bv3Enterprise Parameters All the customer-modifiable InfluxDB v3 Enterprise parameters in Timestream for InfluxDB.
- LogDelivery
Configuration Configuration for sending InfluxDB engine logs to send to specified S3 bucket.
- S3Configuration
Configuration for S3 bucket log delivery.
Enums§
- Cluster
Deployment Type - When writing a match expression against
ClusterDeploymentType, 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. - Cluster
Status - When writing a match expression against
ClusterStatus, 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. - Data
Fusion Runtime Type - When writing a match expression against
DataFusionRuntimeType, 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. - DbInstance
Type - When writing a match expression against
DbInstanceType, 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. - DbStorage
Type - When writing a match expression against
DbStorageType, 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
Type - When writing a match expression against
DeploymentType, 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. - Duration
Type - When writing a match expression against
DurationType, 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. - Engine
Type - When writing a match expression against
EngineType, 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. - Failover
Mode - When writing a match expression against
FailoverMode, 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. - Instance
Mode - When writing a match expression against
InstanceMode, 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. - LogFormats
- When writing a match expression against
LogFormats, 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. - LogLevel
- When writing a match expression against
LogLevel, 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. - Network
Type - When writing a match expression against
NetworkType, 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. - Parameters
The parameters that comprise the parameter group.
- Percent
OrAbsolute Long Percent or Absolute Long for InfluxDB parameters
- Status
- When writing a match expression against
Status, 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. - Tracing
Type - When writing a match expression against
TracingType, 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. - Validation
Exception Reason - When writing a match expression against
ValidationExceptionReason, 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.