Google Native
getCustomerRepricingConfig
Gets information about how a Reseller modifies their bill before sending it to a Customer. Possible Error Codes: * PERMISSION_DENIED: If the account making the request and the account being queried are different. * NOT_FOUND: The CustomerRepricingConfig was not found. * INTERNAL: Any non-user error related to technical issues in the backend. In this case, contact Cloud Channel support. Return Value: If successful, the CustomerRepricingConfig resource, otherwise returns an error.
Using getCustomerRepricingConfig
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getCustomerRepricingConfig(args: GetCustomerRepricingConfigArgs, opts?: InvokeOptions): Promise<GetCustomerRepricingConfigResult>
function getCustomerRepricingConfigOutput(args: GetCustomerRepricingConfigOutputArgs, opts?: InvokeOptions): Output<GetCustomerRepricingConfigResult>
def get_customer_repricing_config(account_id: Optional[str] = None,
customer_id: Optional[str] = None,
customer_repricing_config_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetCustomerRepricingConfigResult
def get_customer_repricing_config_output(account_id: Optional[pulumi.Input[str]] = None,
customer_id: Optional[pulumi.Input[str]] = None,
customer_repricing_config_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetCustomerRepricingConfigResult]
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.
public static class GetCustomerRepricingConfig
{
public static Task<GetCustomerRepricingConfigResult> InvokeAsync(GetCustomerRepricingConfigArgs args, InvokeOptions? opts = null)
public static Output<GetCustomerRepricingConfigResult> Invoke(GetCustomerRepricingConfigInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetCustomerRepricingConfigResult> getCustomerRepricingConfig(GetCustomerRepricingConfigArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
Fn::Invoke:
Function: google-native:cloudchannel/v1:getCustomerRepricingConfig
Arguments:
# Arguments dictionary
The following arguments are supported:
- Account
Id string - Customer
Id string - Customer
Repricing stringConfig Id
- Account
Id string - Customer
Id string - Customer
Repricing stringConfig Id
- account
Id String - customer
Id String - customer
Repricing StringConfig Id
- account
Id string - customer
Id string - customer
Repricing stringConfig Id
- account
Id String - customer
Id String - customer
Repricing StringConfig Id
getCustomerRepricingConfig Result
The following output properties are available:
- Name string
Resource name of the CustomerRepricingConfig. Format: accounts/{account_id}/customers/{customer_id}/customerRepricingConfigs/{id}.
- Repricing
Config Pulumi.Google Native. Cloud Channel. V1. Outputs. Google Cloud Channel V1Repricing Config Response The configuration for bill modifications made by a reseller before sending it to customers.
- Update
Time 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}.
- Repricing
Config GoogleCloud Channel V1Repricing Config Response The configuration for bill modifications made by a reseller before sending it to customers.
- Update
Time 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}.
- repricing
Config GoogleCloud Channel V1Repricing Config Response The configuration for bill modifications made by a reseller before sending it to customers.
- update
Time 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}.
- repricing
Config GoogleCloud Channel V1Repricing Config Response The configuration for bill modifications made by a reseller before sending it to customers.
- update
Time 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 GoogleCloud Channel V1Repricing Config Response 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}.
- repricing
Config Property Map The configuration for bill modifications made by a reseller before sending it to customers.
- update
Time 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.
Supporting Types
GoogleCloudChannelV1PercentageAdjustmentResponse
- Percentage
Pulumi.
Google Native. Cloud Channel. V1. Inputs. Google Type Decimal Response 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
Google
Type Decimal Response 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
Google
Type Decimal Response 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
Google
Type Decimal Response 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
Google
Type Decimal Response 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"
GoogleCloudChannelV1RepricingAdjustmentResponse
- Percentage
Adjustment Pulumi.Google Native. Cloud Channel. V1. Inputs. Google Cloud Channel V1Percentage Adjustment Response Flat markup or markdown on an entire bill.
- Percentage
Adjustment GoogleCloud Channel V1Percentage Adjustment Response Flat markup or markdown on an entire bill.
- percentage
Adjustment GoogleCloud Channel V1Percentage Adjustment Response Flat markup or markdown on an entire bill.
- percentage
Adjustment GoogleCloud Channel V1Percentage Adjustment Response Flat markup or markdown on an entire bill.
- percentage_
adjustment GoogleCloud Channel V1Percentage Adjustment Response Flat markup or markdown on an entire bill.
- percentage
Adjustment Property Map Flat markup or markdown on an entire bill.
GoogleCloudChannelV1RepricingConfigEntitlementGranularityResponse
- 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}
GoogleCloudChannelV1RepricingConfigResponse
- Adjustment
Pulumi.
Google Native. Cloud Channel. V1. Inputs. Google Cloud Channel V1Repricing Adjustment Response Information about the adjustment.
- Channel
Partner Pulumi.Granularity Google Native. Cloud Channel. V1. Inputs. Google Cloud Channel V1Repricing Config Channel Partner Granularity Response Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
- Effective
Invoice Pulumi.Month Google Native. Cloud Channel. V1. Inputs. Google Type Date Response The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
- Entitlement
Granularity Pulumi.Google Native. Cloud Channel. V1. Inputs. Google Cloud Channel V1Repricing Config Entitlement Granularity Response Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.
- Rebilling
Basis string The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
- Adjustment
Google
Cloud Channel V1Repricing Adjustment Response Information about the adjustment.
- Channel
Partner GoogleGranularity Cloud Channel V1Repricing Config Channel Partner Granularity Response Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
- Effective
Invoice GoogleMonth Type Date Response The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
- Entitlement
Granularity GoogleCloud Channel V1Repricing Config Entitlement Granularity Response Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.
- Rebilling
Basis string The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
- adjustment
Google
Cloud Channel V1Repricing Adjustment Response Information about the adjustment.
- channel
Partner GoogleGranularity Cloud Channel V1Repricing Config Channel Partner Granularity Response Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
- effective
Invoice GoogleMonth Type Date Response The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
- entitlement
Granularity GoogleCloud Channel V1Repricing Config Entitlement Granularity Response Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.
- rebilling
Basis String The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
- adjustment
Google
Cloud Channel V1Repricing Adjustment Response Information about the adjustment.
- channel
Partner GoogleGranularity Cloud Channel V1Repricing Config Channel Partner Granularity Response Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
- effective
Invoice GoogleMonth Type Date Response The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
- entitlement
Granularity GoogleCloud Channel V1Repricing Config Entitlement Granularity Response Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.
- rebilling
Basis string The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
- adjustment
Google
Cloud Channel V1Repricing Adjustment Response Information about the adjustment.
- channel_
partner_ Googlegranularity Cloud Channel V1Repricing Config Channel Partner Granularity Response Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
- effective_
invoice_ Googlemonth Type Date Response The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
- entitlement_
granularity GoogleCloud Channel V1Repricing Config Entitlement Granularity Response 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.
- channel
Partner Property MapGranularity Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
- effective
Invoice Property MapMonth The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
- entitlement
Granularity Property Map Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.
- rebilling
Basis String The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
GoogleTypeDateResponse
- 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.
GoogleTypeDecimalResponse
- 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 charactere
(U+0065
) orE
(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 with0
(.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 with400 Bad Request
(INVALID_ARGUMENT
in gRPC) if precision would be lost. Services should error with400 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 charactere
(U+0065
) orE
(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 with0
(.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 with400 Bad Request
(INVALID_ARGUMENT
in gRPC) if precision would be lost. Services should error with400 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 charactere
(U+0065
) orE
(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 with0
(.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 with400 Bad Request
(INVALID_ARGUMENT
in gRPC) if precision would be lost. Services should error with400 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 charactere
(U+0065
) orE
(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 with0
(.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 with400 Bad Request
(INVALID_ARGUMENT
in gRPC) if precision would be lost. Services should error with400 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 charactere
(U+0065
) orE
(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 with0
(.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 with400 Bad Request
(INVALID_ARGUMENT
in gRPC) if precision would be lost. Services should error with400 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 charactere
(U+0065
) orE
(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 with0
(.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 with400 Bad Request
(INVALID_ARGUMENT
in gRPC) if precision would be lost. Services should error with400 Bad Request
(INVALID_ARGUMENT
in gRPC) if the service receives a value outside of the supported range.
Package Details
- Repository
- https://github.com/pulumi/pulumi-google-native
- License
- Apache-2.0