func LookupCustomerRepricingConfig(ctx *Context, args *LookupCustomerRepricingConfigArgs, opts ...InvokeOption) (*LookupCustomerRepricingConfigResult, error)
func LookupCustomerRepricingConfigOutput(ctx *Context, args *LookupCustomerRepricingConfigOutputArgs, opts ...InvokeOption) LookupCustomerRepricingConfigResultOutput

> Note: This function is named LookupCustomerRepricingConfig in the Go SDK.

AccountId string

CustomerId string

CustomerRepricingConfigId string

AccountId string

CustomerId string

CustomerRepricingConfigId string

accountId String

customerId String

customerRepricingConfigId String

accountId string

customerId string

customerRepricingConfigId string

account_id str

customer_id str

customer_repricing_config_id str

accountId String

customerId String

customerRepricingConfigId String

Name string

Resource name of the CustomerRepricingConfig. Format: accounts/{account_id}/customers/{customer_id}/customerRepricingConfigs/{id}.

RepricingConfig Pulumi.GoogleNative.CloudChannel.V1.Outputs.GoogleCloudChannelV1RepricingConfigResponse

The configuration for bill modifications made by a reseller before sending it to customers.

UpdateTime string

Timestamp of an update to the repricing rule. If update_time is after RepricingConfig.effective_invoice_month then it indicates this was set mid-month.

Name string

Resource name of the CustomerRepricingConfig. Format: accounts/{account_id}/customers/{customer_id}/customerRepricingConfigs/{id}.

RepricingConfig GoogleCloudChannelV1RepricingConfigResponse

The configuration for bill modifications made by a reseller before sending it to customers.

UpdateTime string

Timestamp of an update to the repricing rule. If update_time is after RepricingConfig.effective_invoice_month then it indicates this was set mid-month.

name String

Resource name of the CustomerRepricingConfig. Format: accounts/{account_id}/customers/{customer_id}/customerRepricingConfigs/{id}.

repricingConfig GoogleCloudChannelV1RepricingConfigResponse

The configuration for bill modifications made by a reseller before sending it to customers.

updateTime String

Timestamp of an update to the repricing rule. If update_time is after RepricingConfig.effective_invoice_month then it indicates this was set mid-month.

name string

Resource name of the CustomerRepricingConfig. Format: accounts/{account_id}/customers/{customer_id}/customerRepricingConfigs/{id}.

repricingConfig GoogleCloudChannelV1RepricingConfigResponse

The configuration for bill modifications made by a reseller before sending it to customers.

updateTime string

Timestamp of an update to the repricing rule. If update_time is after RepricingConfig.effective_invoice_month then it indicates this was set mid-month.

name str

Resource name of the CustomerRepricingConfig. Format: accounts/{account_id}/customers/{customer_id}/customerRepricingConfigs/{id}.

repricing_config GoogleCloudChannelV1RepricingConfigResponse

The configuration for bill modifications made by a reseller before sending it to customers.

update_time str

Timestamp of an update to the repricing rule. If update_time is after RepricingConfig.effective_invoice_month then it indicates this was set mid-month.

name String

Resource name of the CustomerRepricingConfig. Format: accounts/{account_id}/customers/{customer_id}/customerRepricingConfigs/{id}.

repricingConfig Property Map

The configuration for bill modifications made by a reseller before sending it to customers.

updateTime String

Timestamp of an update to the repricing rule. If update_time is after RepricingConfig.effective_invoice_month then it indicates this was set mid-month.

Percentage Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleTypeDecimalResponse

The percentage of the bill to adjust. For example: Mark down by 1% => "-1.00" Mark up by 1% => "1.00" Pass-Through => "0.00"

Percentage GoogleTypeDecimalResponse

The percentage of the bill to adjust. For example: Mark down by 1% => "-1.00" Mark up by 1% => "1.00" Pass-Through => "0.00"

percentage GoogleTypeDecimalResponse

The percentage of the bill to adjust. For example: Mark down by 1% => "-1.00" Mark up by 1% => "1.00" Pass-Through => "0.00"

percentage GoogleTypeDecimalResponse

The percentage of the bill to adjust. For example: Mark down by 1% => "-1.00" Mark up by 1% => "1.00" Pass-Through => "0.00"

percentage GoogleTypeDecimalResponse

The percentage of the bill to adjust. For example: Mark down by 1% => "-1.00" Mark up by 1% => "1.00" Pass-Through => "0.00"

percentage Property Map

The percentage of the bill to adjust. For example: Mark down by 1% => "-1.00" Mark up by 1% => "1.00" Pass-Through => "0.00"

PercentageAdjustment Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1PercentageAdjustmentResponse

Flat markup or markdown on an entire bill.

PercentageAdjustment GoogleCloudChannelV1PercentageAdjustmentResponse

Flat markup or markdown on an entire bill.

percentageAdjustment GoogleCloudChannelV1PercentageAdjustmentResponse

Flat markup or markdown on an entire bill.

percentageAdjustment GoogleCloudChannelV1PercentageAdjustmentResponse

Flat markup or markdown on an entire bill.

percentage_adjustment GoogleCloudChannelV1PercentageAdjustmentResponse

Flat markup or markdown on an entire bill.

percentageAdjustment Property Map

Flat markup or markdown on an entire bill.

Entitlement string

Resource name of the entitlement. Format: accounts/{account_id}/customers/{customer_id}/entitlements/{entitlement_id}

Entitlement string

Resource name of the entitlement. Format: accounts/{account_id}/customers/{customer_id}/entitlements/{entitlement_id}

entitlement String

Resource name of the entitlement. Format: accounts/{account_id}/customers/{customer_id}/entitlements/{entitlement_id}

entitlement string

Resource name of the entitlement. Format: accounts/{account_id}/customers/{customer_id}/entitlements/{entitlement_id}

entitlement str

Resource name of the entitlement. Format: accounts/{account_id}/customers/{customer_id}/entitlements/{entitlement_id}

entitlement String

Resource name of the entitlement. Format: accounts/{account_id}/customers/{customer_id}/entitlements/{entitlement_id}

Adjustment Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1RepricingAdjustmentResponse

Information about the adjustment.

ChannelPartnerGranularity Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1RepricingConfigChannelPartnerGranularityResponse

Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.

EffectiveInvoiceMonth Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleTypeDateResponse

The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.

EntitlementGranularity Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1RepricingConfigEntitlementGranularityResponse

Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

RebillingBasis string

The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.

Adjustment GoogleCloudChannelV1RepricingAdjustmentResponse

Information about the adjustment.

ChannelPartnerGranularity GoogleCloudChannelV1RepricingConfigChannelPartnerGranularityResponse

Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.

EffectiveInvoiceMonth GoogleTypeDateResponse

The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.

EntitlementGranularity GoogleCloudChannelV1RepricingConfigEntitlementGranularityResponse

Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

RebillingBasis string

The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.

adjustment GoogleCloudChannelV1RepricingAdjustmentResponse

Information about the adjustment.

channelPartnerGranularity GoogleCloudChannelV1RepricingConfigChannelPartnerGranularityResponse

Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.

effectiveInvoiceMonth GoogleTypeDateResponse

The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.

entitlementGranularity GoogleCloudChannelV1RepricingConfigEntitlementGranularityResponse

Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

rebillingBasis String

The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.

adjustment GoogleCloudChannelV1RepricingAdjustmentResponse

Information about the adjustment.

channelPartnerGranularity GoogleCloudChannelV1RepricingConfigChannelPartnerGranularityResponse

Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.

effectiveInvoiceMonth GoogleTypeDateResponse

The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.

entitlementGranularity GoogleCloudChannelV1RepricingConfigEntitlementGranularityResponse

Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

rebillingBasis string

The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.

adjustment GoogleCloudChannelV1RepricingAdjustmentResponse

Information about the adjustment.

channel_partner_granularity GoogleCloudChannelV1RepricingConfigChannelPartnerGranularityResponse

Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.

effective_invoice_month GoogleTypeDateResponse

The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.

entitlement_granularity GoogleCloudChannelV1RepricingConfigEntitlementGranularityResponse

Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

rebilling_basis str

The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.

adjustment Property Map

Information about the adjustment.

channelPartnerGranularity Property Map

Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.

effectiveInvoiceMonth Property Map

The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.

entitlementGranularity Property Map

Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

rebillingBasis String

The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.

Day int

Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.

Month int

Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.

Year int

Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.

Day int

Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.

Month int

Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.

Year int

Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.

day Integer

Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.

month Integer

Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.

year Integer

Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.

day number

Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.

month number

Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.

year number

Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.

day int

Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.

month int

Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.

year int

Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.

day Number

Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.

month Number

Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.

year Number

Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.

Value string

The decimal value, as a string. The string representation consists of an optional sign, + (U+002B) or - (U+002D), followed by a sequence of zero or more decimal digits ("the integer"), optionally followed by a fraction, optionally followed by an exponent. The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand. The exponent consists of the character e (U+0065) or E (U+0045) followed by one or more decimal digits. Services should normalize decimal values before storing them by: - Removing an explicitly-provided + sign (+2.5 -> 2.5). - Replacing a zero-length integer value with 0 (.5 -> 0.5). - Coercing the exponent character to lower-case (2.5E8 -> 2.5e8). - Removing an explicitly-provided zero exponent (2.5e0 -> 2.5). Services may perform additional normalization based on its own needs and the internal decimal implementation selected, such as shifting the decimal point and exponent value together (example: 2.5e-1 <-> 0.25). Additionally, services may preserve trailing zeroes in the fraction to indicate increased precision, but are not required to do so. Note that only the . character is supported to divide the integer and the fraction; , should not be supported regardless of locale. Additionally, thousand separators should not be supported. If a service does support them, values must be normalized. The ENBF grammar is: DecimalString = [Sign] Significand [Exponent]; Sign = '+' | '-'; Significand = Digits '.' | [Digits] '.' Digits; Exponent = ('e' | 'E') [Sign] Digits; Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' }; Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values. Services may choose to accept values passed as input even when the value has a higher precision or scale than the service supports, and should round the value to fit the supported scale. Alternatively, the service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if precision would be lost. Services should error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if the service receives a value outside of the supported range.

Value string

The decimal value, as a string. The string representation consists of an optional sign, + (U+002B) or - (U+002D), followed by a sequence of zero or more decimal digits ("the integer"), optionally followed by a fraction, optionally followed by an exponent. The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand. The exponent consists of the character e (U+0065) or E (U+0045) followed by one or more decimal digits. Services should normalize decimal values before storing them by: - Removing an explicitly-provided + sign (+2.5 -> 2.5). - Replacing a zero-length integer value with 0 (.5 -> 0.5). - Coercing the exponent character to lower-case (2.5E8 -> 2.5e8). - Removing an explicitly-provided zero exponent (2.5e0 -> 2.5). Services may perform additional normalization based on its own needs and the internal decimal implementation selected, such as shifting the decimal point and exponent value together (example: 2.5e-1 <-> 0.25). Additionally, services may preserve trailing zeroes in the fraction to indicate increased precision, but are not required to do so. Note that only the . character is supported to divide the integer and the fraction; , should not be supported regardless of locale. Additionally, thousand separators should not be supported. If a service does support them, values must be normalized. The ENBF grammar is: DecimalString = [Sign] Significand [Exponent]; Sign = '+' | '-'; Significand = Digits '.' | [Digits] '.' Digits; Exponent = ('e' | 'E') [Sign] Digits; Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' }; Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values. Services may choose to accept values passed as input even when the value has a higher precision or scale than the service supports, and should round the value to fit the supported scale. Alternatively, the service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if precision would be lost. Services should error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if the service receives a value outside of the supported range.

value String

The decimal value, as a string. The string representation consists of an optional sign, + (U+002B) or - (U+002D), followed by a sequence of zero or more decimal digits ("the integer"), optionally followed by a fraction, optionally followed by an exponent. The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand. The exponent consists of the character e (U+0065) or E (U+0045) followed by one or more decimal digits. Services should normalize decimal values before storing them by: - Removing an explicitly-provided + sign (+2.5 -> 2.5). - Replacing a zero-length integer value with 0 (.5 -> 0.5). - Coercing the exponent character to lower-case (2.5E8 -> 2.5e8). - Removing an explicitly-provided zero exponent (2.5e0 -> 2.5). Services may perform additional normalization based on its own needs and the internal decimal implementation selected, such as shifting the decimal point and exponent value together (example: 2.5e-1 <-> 0.25). Additionally, services may preserve trailing zeroes in the fraction to indicate increased precision, but are not required to do so. Note that only the . character is supported to divide the integer and the fraction; , should not be supported regardless of locale. Additionally, thousand separators should not be supported. If a service does support them, values must be normalized. The ENBF grammar is: DecimalString = [Sign] Significand [Exponent]; Sign = '+' | '-'; Significand = Digits '.' | [Digits] '.' Digits; Exponent = ('e' | 'E') [Sign] Digits; Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' }; Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values. Services may choose to accept values passed as input even when the value has a higher precision or scale than the service supports, and should round the value to fit the supported scale. Alternatively, the service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if precision would be lost. Services should error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if the service receives a value outside of the supported range.

value string

The decimal value, as a string. The string representation consists of an optional sign, + (U+002B) or - (U+002D), followed by a sequence of zero or more decimal digits ("the integer"), optionally followed by a fraction, optionally followed by an exponent. The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand. The exponent consists of the character e (U+0065) or E (U+0045) followed by one or more decimal digits. Services should normalize decimal values before storing them by: - Removing an explicitly-provided + sign (+2.5 -> 2.5). - Replacing a zero-length integer value with 0 (.5 -> 0.5). - Coercing the exponent character to lower-case (2.5E8 -> 2.5e8). - Removing an explicitly-provided zero exponent (2.5e0 -> 2.5). Services may perform additional normalization based on its own needs and the internal decimal implementation selected, such as shifting the decimal point and exponent value together (example: 2.5e-1 <-> 0.25). Additionally, services may preserve trailing zeroes in the fraction to indicate increased precision, but are not required to do so. Note that only the . character is supported to divide the integer and the fraction; , should not be supported regardless of locale. Additionally, thousand separators should not be supported. If a service does support them, values must be normalized. The ENBF grammar is: DecimalString = [Sign] Significand [Exponent]; Sign = '+' | '-'; Significand = Digits '.' | [Digits] '.' Digits; Exponent = ('e' | 'E') [Sign] Digits; Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' }; Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values. Services may choose to accept values passed as input even when the value has a higher precision or scale than the service supports, and should round the value to fit the supported scale. Alternatively, the service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if precision would be lost. Services should error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if the service receives a value outside of the supported range.

value str

The decimal value, as a string. The string representation consists of an optional sign, + (U+002B) or - (U+002D), followed by a sequence of zero or more decimal digits ("the integer"), optionally followed by a fraction, optionally followed by an exponent. The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand. The exponent consists of the character e (U+0065) or E (U+0045) followed by one or more decimal digits. Services should normalize decimal values before storing them by: - Removing an explicitly-provided + sign (+2.5 -> 2.5). - Replacing a zero-length integer value with 0 (.5 -> 0.5). - Coercing the exponent character to lower-case (2.5E8 -> 2.5e8). - Removing an explicitly-provided zero exponent (2.5e0 -> 2.5). Services may perform additional normalization based on its own needs and the internal decimal implementation selected, such as shifting the decimal point and exponent value together (example: 2.5e-1 <-> 0.25). Additionally, services may preserve trailing zeroes in the fraction to indicate increased precision, but are not required to do so. Note that only the . character is supported to divide the integer and the fraction; , should not be supported regardless of locale. Additionally, thousand separators should not be supported. If a service does support them, values must be normalized. The ENBF grammar is: DecimalString = [Sign] Significand [Exponent]; Sign = '+' | '-'; Significand = Digits '.' | [Digits] '.' Digits; Exponent = ('e' | 'E') [Sign] Digits; Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' }; Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values. Services may choose to accept values passed as input even when the value has a higher precision or scale than the service supports, and should round the value to fit the supported scale. Alternatively, the service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if precision would be lost. Services should error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if the service receives a value outside of the supported range.

value String

The decimal value, as a string. The string representation consists of an optional sign, + (U+002B) or - (U+002D), followed by a sequence of zero or more decimal digits ("the integer"), optionally followed by a fraction, optionally followed by an exponent. The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand. The exponent consists of the character e (U+0065) or E (U+0045) followed by one or more decimal digits. Services should normalize decimal values before storing them by: - Removing an explicitly-provided + sign (+2.5 -> 2.5). - Replacing a zero-length integer value with 0 (.5 -> 0.5). - Coercing the exponent character to lower-case (2.5E8 -> 2.5e8). - Removing an explicitly-provided zero exponent (2.5e0 -> 2.5). Services may perform additional normalization based on its own needs and the internal decimal implementation selected, such as shifting the decimal point and exponent value together (example: 2.5e-1 <-> 0.25). Additionally, services may preserve trailing zeroes in the fraction to indicate increased precision, but are not required to do so. Note that only the . character is supported to divide the integer and the fraction; , should not be supported regardless of locale. Additionally, thousand separators should not be supported. If a service does support them, values must be normalized. The ENBF grammar is: DecimalString = [Sign] Significand [Exponent]; Sign = '+' | '-'; Significand = Digits '.' | [Digits] '.' Digits; Exponent = ('e' | 'E') [Sign] Digits; Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' }; Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values. Services may choose to accept values passed as input even when the value has a higher precision or scale than the service supports, and should round the value to fit the supported scale. Alternatively, the service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if precision would be lost. Services should error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if the service receives a value outside of the supported range.