1. Packages
  2. Google Cloud Native
  3. API Docs
  4. cloudchannel
  5. cloudchannel/v1
  6. getCustomerRepricingConfig

Google Cloud Native is in preview. Google Cloud Classic is fully supported.

Google Cloud Native v0.31.1 published on Thursday, Jul 20, 2023 by Pulumi

google-native.cloudchannel/v1.getCustomerRepricingConfig

Explore with Pulumi AI

google-native logo

Google Cloud Native is in preview. Google Cloud Classic is fully supported.

Google Cloud Native v0.31.1 published on Thursday, Jul 20, 2023 by Pulumi

    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:

    getCustomerRepricingConfig Result

    The following output properties are available:

    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.

    Supporting Types

    GoogleCloudChannelV1ConditionalOverrideResponse

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

    Information about the applied override's adjustment.

    RebillingBasis string

    The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.

    RepricingCondition Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1RepricingConditionResponse

    Specifies the condition which, if met, will apply the override.

    Adjustment GoogleCloudChannelV1RepricingAdjustmentResponse

    Information about the applied override's adjustment.

    RebillingBasis string

    The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.

    RepricingCondition GoogleCloudChannelV1RepricingConditionResponse

    Specifies the condition which, if met, will apply the override.

    adjustment GoogleCloudChannelV1RepricingAdjustmentResponse

    Information about the applied override's adjustment.

    rebillingBasis String

    The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.

    repricingCondition GoogleCloudChannelV1RepricingConditionResponse

    Specifies the condition which, if met, will apply the override.

    adjustment GoogleCloudChannelV1RepricingAdjustmentResponse

    Information about the applied override's adjustment.

    rebillingBasis string

    The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.

    repricingCondition GoogleCloudChannelV1RepricingConditionResponse

    Specifies the condition which, if met, will apply the override.

    adjustment GoogleCloudChannelV1RepricingAdjustmentResponse

    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 GoogleCloudChannelV1RepricingConditionResponse

    Specifies the condition which, if met, will apply the override.

    adjustment Property Map

    Information about the applied override's adjustment.

    rebillingBasis String

    The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.

    repricingCondition Property Map

    Specifies the condition which, if met, will apply the override.

    GoogleCloudChannelV1PercentageAdjustmentResponse

    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"

    GoogleCloudChannelV1RepricingAdjustmentResponse

    percentageAdjustment Property Map

    Flat markup or markdown on an entire bill.

    GoogleCloudChannelV1RepricingConditionResponse

    skuGroupCondition Property Map

    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.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.

    ConditionalOverrides List<Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1ConditionalOverrideResponse>

    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.

    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.

    ConditionalOverrides []GoogleCloudChannelV1ConditionalOverrideResponse

    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.

    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.

    conditionalOverrides List<GoogleCloudChannelV1ConditionalOverrideResponse>

    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.

    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.

    conditionalOverrides GoogleCloudChannelV1ConditionalOverrideResponse[]

    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.

    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.

    conditional_overrides Sequence[GoogleCloudChannelV1ConditionalOverrideResponse]

    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_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.

    conditionalOverrides 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.

    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.

    GoogleCloudChannelV1SkuGroupConditionResponse

    SkuGroup 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".

    SkuGroup 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".

    skuGroup 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".

    skuGroup 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".

    skuGroup 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 as 0. 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 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 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. An empty string should be interpreted as 0. 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 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 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. An empty string should be interpreted as 0. 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 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 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. An empty string should be interpreted as 0. 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 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 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. An empty string should be interpreted as 0. 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 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 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. An empty string should be interpreted as 0. 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 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 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.

    Package Details

    Repository
    Google Cloud Native pulumi/pulumi-google-native
    License
    Apache-2.0
    google-native logo

    Google Cloud Native is in preview. Google Cloud Classic is fully supported.

    Google Cloud Native v0.31.1 published on Thursday, Jul 20, 2023 by Pulumi