Google Cloud Native is in preview. Google Cloud Classic is fully supported.
google-native.cloudchannel/v1.getChannelPartnerRepricingConfig
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Gets information about how a Distributor modifies their bill before sending it to a ChannelPartner. Possible Error Codes: * PERMISSION_DENIED: If the account making the request and the account being queried are different. * NOT_FOUND: The ChannelPartnerRepricingConfig 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 ChannelPartnerRepricingConfig resource, otherwise returns an error.
Using getChannelPartnerRepricingConfig
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 getChannelPartnerRepricingConfig(args: GetChannelPartnerRepricingConfigArgs, opts?: InvokeOptions): Promise<GetChannelPartnerRepricingConfigResult>
function getChannelPartnerRepricingConfigOutput(args: GetChannelPartnerRepricingConfigOutputArgs, opts?: InvokeOptions): Output<GetChannelPartnerRepricingConfigResult>
def get_channel_partner_repricing_config(account_id: Optional[str] = None,
channel_partner_link_id: Optional[str] = None,
channel_partner_repricing_config_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetChannelPartnerRepricingConfigResult
def get_channel_partner_repricing_config_output(account_id: Optional[pulumi.Input[str]] = None,
channel_partner_link_id: Optional[pulumi.Input[str]] = None,
channel_partner_repricing_config_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetChannelPartnerRepricingConfigResult]
func LookupChannelPartnerRepricingConfig(ctx *Context, args *LookupChannelPartnerRepricingConfigArgs, opts ...InvokeOption) (*LookupChannelPartnerRepricingConfigResult, error)
func LookupChannelPartnerRepricingConfigOutput(ctx *Context, args *LookupChannelPartnerRepricingConfigOutputArgs, opts ...InvokeOption) LookupChannelPartnerRepricingConfigResultOutput
> Note: This function is named LookupChannelPartnerRepricingConfig
in the Go SDK.
public static class GetChannelPartnerRepricingConfig
{
public static Task<GetChannelPartnerRepricingConfigResult> InvokeAsync(GetChannelPartnerRepricingConfigArgs args, InvokeOptions? opts = null)
public static Output<GetChannelPartnerRepricingConfigResult> Invoke(GetChannelPartnerRepricingConfigInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetChannelPartnerRepricingConfigResult> getChannelPartnerRepricingConfig(GetChannelPartnerRepricingConfigArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: google-native:cloudchannel/v1:getChannelPartnerRepricingConfig
arguments:
# arguments dictionary
The following arguments are supported:
- Account
Id string - Channel
Partner stringLink Id - Channel
Partner stringRepricing Config Id
- Account
Id string - Channel
Partner stringLink Id - Channel
Partner stringRepricing Config Id
- account
Id String - channel
Partner StringLink Id - channel
Partner StringRepricing Config Id
- account
Id string - channel
Partner stringLink Id - channel
Partner stringRepricing Config Id
- account
Id String - channel
Partner StringLink Id - channel
Partner StringRepricing Config Id
getChannelPartnerRepricingConfig Result
The following output properties are available:
- Name string
- Resource name of the ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{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 ChannelPartner.
- 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 ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
- Repricing
Config GoogleCloud Channel V1Repricing Config Response - The configuration for bill modifications made by a reseller before sending it to ChannelPartner.
- 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 ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
- repricing
Config GoogleCloud Channel V1Repricing Config Response - The configuration for bill modifications made by a reseller before sending it to ChannelPartner.
- 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 ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
- repricing
Config GoogleCloud Channel V1Repricing Config Response - The configuration for bill modifications made by a reseller before sending it to ChannelPartner.
- 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 ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
- repricing_
config GoogleCloud Channel V1Repricing Config Response - The configuration for bill modifications made by a reseller before sending it to ChannelPartner.
- 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 ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
- repricing
Config Property Map - The configuration for bill modifications made by a reseller before sending it to ChannelPartner.
- 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
GoogleCloudChannelV1ConditionalOverrideResponse
- Adjustment
Pulumi.
Google Native. Cloud Channel. V1. Inputs. Google Cloud Channel V1Repricing Adjustment Response - Information about the applied override's adjustment.
- Rebilling
Basis string - The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
- Repricing
Condition Pulumi.Google Native. Cloud Channel. V1. Inputs. Google Cloud Channel V1Repricing Condition Response - Specifies the condition which, if met, will apply the override.
- Adjustment
Google
Cloud Channel V1Repricing Adjustment Response - Information about the applied override's adjustment.
- Rebilling
Basis string - The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
- Repricing
Condition GoogleCloud Channel V1Repricing Condition Response - Specifies the condition which, if met, will apply the override.
- adjustment
Google
Cloud Channel V1Repricing Adjustment Response - Information about the applied override's adjustment.
- rebilling
Basis String - The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
- repricing
Condition GoogleCloud Channel V1Repricing Condition Response - Specifies the condition which, if met, will apply the override.
- adjustment
Google
Cloud Channel V1Repricing Adjustment Response - Information about the applied override's adjustment.
- rebilling
Basis string - The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
- repricing
Condition GoogleCloud Channel V1Repricing Condition Response - Specifies the condition which, if met, will apply the override.
- adjustment
Google
Cloud Channel V1Repricing Adjustment Response - Information about the applied override's adjustment.
- rebilling_
basis str - The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
- repricing_
condition GoogleCloud Channel V1Repricing Condition Response - Specifies the condition which, if met, will apply the override.
- adjustment Property Map
- Information about the applied override's adjustment.
- rebilling
Basis String - The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
- repricing
Condition Property Map - Specifies the condition which, if met, will apply the override.
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.
GoogleCloudChannelV1RepricingConditionResponse
- Sku
Group Pulumi.Condition Google Native. Cloud Channel. V1. Inputs. Google Cloud Channel V1Sku Group Condition Response - SKU Group condition for override.
- Sku
Group GoogleCondition Cloud Channel V1Sku Group Condition Response - SKU Group condition for override.
- sku
Group GoogleCondition Cloud Channel V1Sku Group Condition Response - SKU Group condition for override.
- sku
Group GoogleCondition Cloud Channel V1Sku Group Condition Response - SKU Group condition for override.
- sku_
group_ Googlecondition Cloud Channel V1Sku Group Condition Response - SKU Group condition for override.
- sku
Group Property MapCondition - SKU Group condition for override.
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. Only ChannelPartnerRepricingConfig supports this value. Deprecated: This is no longer supported. Use RepricingConfig.entitlement_granularity instead.
- Conditional
Overrides List<Pulumi.Google Native. Cloud Channel. V1. Inputs. Google Cloud Channel V1Conditional Override Response> - The conditional overrides to apply for this configuration. If you list multiple overrides, only the first valid override is used. If you don't list any overrides, the API uses the normal adjustment and rebilling basis.
- 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. Note: If a ChannelPartnerRepricingConfig using RepricingConfig.EntitlementGranularity becomes effective, then no existing or future RepricingConfig.ChannelPartnerGranularity will apply to the RepricingConfig.EntitlementGranularity.entitlement. This is the recommended value for both CustomerRepricingConfig and ChannelPartnerRepricingConfig.
- 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. Only ChannelPartnerRepricingConfig supports this value. Deprecated: This is no longer supported. Use RepricingConfig.entitlement_granularity instead.
- Conditional
Overrides []GoogleCloud Channel V1Conditional Override Response - The conditional overrides to apply for this configuration. If you list multiple overrides, only the first valid override is used. If you don't list any overrides, the API uses the normal adjustment and rebilling basis.
- 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. Note: If a ChannelPartnerRepricingConfig using RepricingConfig.EntitlementGranularity becomes effective, then no existing or future RepricingConfig.ChannelPartnerGranularity will apply to the RepricingConfig.EntitlementGranularity.entitlement. This is the recommended value for both CustomerRepricingConfig and ChannelPartnerRepricingConfig.
- 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. Only ChannelPartnerRepricingConfig supports this value. Deprecated: This is no longer supported. Use RepricingConfig.entitlement_granularity instead.
- conditional
Overrides List<GoogleCloud Channel V1Conditional Override Response> - The conditional overrides to apply for this configuration. If you list multiple overrides, only the first valid override is used. If you don't list any overrides, the API uses the normal adjustment and rebilling basis.
- 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. Note: If a ChannelPartnerRepricingConfig using RepricingConfig.EntitlementGranularity becomes effective, then no existing or future RepricingConfig.ChannelPartnerGranularity will apply to the RepricingConfig.EntitlementGranularity.entitlement. This is the recommended value for both CustomerRepricingConfig and ChannelPartnerRepricingConfig.
- 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. Only ChannelPartnerRepricingConfig supports this value. Deprecated: This is no longer supported. Use RepricingConfig.entitlement_granularity instead.
- conditional
Overrides GoogleCloud Channel V1Conditional Override Response[] - The conditional overrides to apply for this configuration. If you list multiple overrides, only the first valid override is used. If you don't list any overrides, the API uses the normal adjustment and rebilling basis.
- 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. Note: If a ChannelPartnerRepricingConfig using RepricingConfig.EntitlementGranularity becomes effective, then no existing or future RepricingConfig.ChannelPartnerGranularity will apply to the RepricingConfig.EntitlementGranularity.entitlement. This is the recommended value for both CustomerRepricingConfig and ChannelPartnerRepricingConfig.
- 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. Only ChannelPartnerRepricingConfig supports this value. Deprecated: This is no longer supported. Use RepricingConfig.entitlement_granularity instead.
- conditional_
overrides Sequence[GoogleCloud Channel V1Conditional Override Response] - The conditional overrides to apply for this configuration. If you list multiple overrides, only the first valid override is used. If you don't list any overrides, the API uses the normal adjustment and rebilling basis.
- 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. Note: If a ChannelPartnerRepricingConfig using RepricingConfig.EntitlementGranularity becomes effective, then no existing or future RepricingConfig.ChannelPartnerGranularity will apply to the RepricingConfig.EntitlementGranularity.entitlement. This is the recommended value for both CustomerRepricingConfig and ChannelPartnerRepricingConfig.
- 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. Only ChannelPartnerRepricingConfig supports this value. Deprecated: This is no longer supported. Use RepricingConfig.entitlement_granularity instead.
- conditional
Overrides List<Property Map> - The conditional overrides to apply for this configuration. If you list multiple overrides, only the first valid override is used. If you don't list any overrides, the API uses the normal adjustment and rebilling basis.
- 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. Note: If a ChannelPartnerRepricingConfig using RepricingConfig.EntitlementGranularity becomes effective, then no existing or future RepricingConfig.ChannelPartnerGranularity will apply to the RepricingConfig.EntitlementGranularity.entitlement. This is the recommended value for both CustomerRepricingConfig and ChannelPartnerRepricingConfig.
- rebilling
Basis String - The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
GoogleCloudChannelV1SkuGroupConditionResponse
- Sku
Group string - Specifies a SKU group (https://cloud.google.com/skus/sku-groups). Resource name of SKU group. Format: accounts/{account}/skuGroups/{sku_group}. Example: "accounts/C01234/skuGroups/3d50fd57-3157-4577-a5a9-a219b8490041".
- Sku
Group string - Specifies a SKU group (https://cloud.google.com/skus/sku-groups). Resource name of SKU group. Format: accounts/{account}/skuGroups/{sku_group}. Example: "accounts/C01234/skuGroups/3d50fd57-3157-4577-a5a9-a219b8490041".
- sku
Group String - Specifies a SKU group (https://cloud.google.com/skus/sku-groups). Resource name of SKU group. Format: accounts/{account}/skuGroups/{sku_group}. Example: "accounts/C01234/skuGroups/3d50fd57-3157-4577-a5a9-a219b8490041".
- sku
Group string - Specifies a SKU group (https://cloud.google.com/skus/sku-groups). Resource name of SKU group. Format: accounts/{account}/skuGroups/{sku_group}. Example: "accounts/C01234/skuGroups/3d50fd57-3157-4577-a5a9-a219b8490041".
- sku_
group str - Specifies a SKU group (https://cloud.google.com/skus/sku-groups). Resource name of SKU group. Format: accounts/{account}/skuGroups/{sku_group}. Example: "accounts/C01234/skuGroups/3d50fd57-3157-4577-a5a9-a219b8490041".
- sku
Group String - Specifies a SKU group (https://cloud.google.com/skus/sku-groups). Resource name of SKU group. Format: accounts/{account}/skuGroups/{sku_group}. Example: "accounts/C01234/skuGroups/3d50fd57-3157-4577-a5a9-a219b8490041".
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. An empty string should be interpreted as0
. 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 upper-case, with explicit sign (2.5e8
->2.5E+8
). - 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. An empty string should be interpreted as0
. 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 upper-case, with explicit sign (2.5e8
->2.5E+8
). - 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. An empty string should be interpreted as0
. 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 upper-case, with explicit sign (2.5e8
->2.5E+8
). - 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. An empty string should be interpreted as0
. 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 upper-case, with explicit sign (2.5e8
->2.5E+8
). - 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. An empty string should be interpreted as0
. 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 upper-case, with explicit sign (2.5e8
->2.5E+8
). - 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. An empty string should be interpreted as0
. 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 upper-case, with explicit sign (2.5e8
->2.5E+8
). - 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
- Google Cloud Native pulumi/pulumi-google-native
- License
- Apache-2.0
Google Cloud Native is in preview. Google Cloud Classic is fully supported.