Module aws_sdk_billingconductor::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules
- Builders
- Error types that AWSBillingConductor can respond with.
Structs
A representation of a linked account.
The set of accounts that will be under the billing group. The set of accounts resemble the linked accounts in a consolidated billing family.
A representation of a resource association error.
A resource association result for a percentage custom line item.
A summary report of actual Amazon Web Services charges and calculated Amazon Web Services charges, based on the associated pricing plan of a billing group.
A representation of a billing group.
The preferences and settings that will be used to compute the Amazon Web Services charges for a billing group.
The possible Amazon Web Services Free Tier configurations.
The set of tiering configurations for the pricing rule.
The billing period range in which the custom line item request will be applied.
The charge details of a custom line item. It should contain only one of
Flat
orPercentage
.A representation of the charge details that are associated with a flat custom line item.
A representation of a custom line item.
A representation of the charge details that are associated with a percentage custom line item.
A representation of a custom line item version.
A resource disassociation result for a percentage custom line item.
The possible Amazon Web Services Free Tier configurations.
A representation of the line item filter for your custom line item. You can use line item filters to include or exclude specific resource values from the billing group's total cost. For example, if you create a custom line item and you want to filter out a value, such as Savings Plan discounts, you can update
LineItemFilter
to exclude it.The filter on the account ID of the linked account, or any of the following:
Specifies if the billing group has the following features enabled.
The filter used to retrieve specific
BillingGroupCostReportElements
.The filter that specifies the billing groups and pricing plans to retrieve billing group information.
A representation of the charge details of a custom line item.
A representation of the charge details that are associated with a flat custom line item.
A representation of the charge details that are associated with a percentage custom line item.
A billing period filter that specifies the custom line item versions to retrieve.
A filter that specifies the billing period range where the custom line item versions reside.
A filter that specifies the custom line items and billing groups to retrieve FFLI information.
The filter that specifies the Amazon Resource Names (ARNs) of pricing plans, to retrieve pricing plan information.
The filter that specifies criteria that the pricing rules returned by the
ListPricingRules
API will adhere to.A filter that specifies the type of resource associations that should be retrieved for a custom line item.
A representation of a resource association for a custom line item.
A representation of a pricing plan.
A representation of a pricing rule.
The set of tiering configurations for the pricing rule.
Specifies if the billing group has the following features enabled.
A representation of the new charge details of a custom line item. This should contain only one of
Flat
orPercentage
.A representation of the new charge details that are associated with a flat custom line item.
A representation of the new charge details that are associated with a percentage custom line item.
The possible Amazon Web Services Free Tier configurations.
The set of tiering configurations for the pricing rule.
The field's information of a request that resulted in an exception.
Enums
- When writing a match expression against
AssociateResourceErrorReason
, 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 against
BillingGroupStatus
, 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 against
ConflictExceptionReason
, 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 against
CurrencyCode
, 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 against
CustomLineItemRelationship
, 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 against
CustomLineItemType
, 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 against
LineItemFilterAttributeName
, 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 against
LineItemFilterValue
, 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 against
MatchOption
, 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 against
PricingRuleScope
, 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 against
PricingRuleType
, 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 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.