Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Active
Time Range A time range with a start and end time.
- Billing
View Element The metadata associated to the billing view.
- Billing
View Health Status Represents the health status of a billing view, including a status code and optional reasons for the status.
- Billing
View List Element A representation of a billing view.
- Dimension
Values The metadata that you can use to filter and group your results.
- Expression
See Expression. Billing view only supports
LINKED_ACCOUNTandTags.- Resource
Tag The tag structure that contains a tag key and value.
- String
Search A structure that defines how to search for string values. You can specify a search option and the value to search for.
- TagValues
The values that are available for a tag.
- Time
Range Specifies a time range with inclusive begin and end dates.
- Validation
Exception Field The field's information of a request that resulted in an exception.
Enums§
- Billing
View Status - When writing a match expression against
BillingViewStatus, 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. - Billing
View Status Reason - When writing a match expression against
BillingViewStatusReason, 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. - Billing
View Type - When writing a match expression against
BillingViewType, 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. - Dimension
- When writing a match expression against
Dimension, 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. - Search
Option - When writing a match expression against
SearchOption, 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.