Google Cloud Native v0.28.0, Feb 2 23

google-native.cloudchannel/v1.ChannelPartnerRepricingConfig

Creates a ChannelPartnerRepricingConfig. Call this method to set modifications for a specific ChannelPartner’s bill. You can only create configs if the RepricingConfig.effective_invoice_month is a future month. If needed, you can create a config for the current month, with some restrictions. When creating a config for a future month, make sure there are no existing configs for that RepricingConfig.effective_invoice_month. The following restrictions are for creating configs in the current month. * This functionality is reserved for recovering from an erroneous config, and should not be used for regular business cases. * The new config will not modify exports used with other configs. Changes to the config may be immediate, but may take up to 24 hours. * There is a limit of ten configs for any ChannelPartner or RepricingConfig.effective_invoice_month. * The contained ChannelPartnerRepricingConfig.repricing_config vaule must be different from the value used in the current config for a ChannelPartner. Possible Error Codes: * PERMISSION_DENIED: If the account making the request and the account being queried are different. * INVALID_ARGUMENT: Missing or invalid required parameters in the request. Also displays if the updated config is for the current month or past months. * NOT_FOUND: The ChannelPartnerRepricingConfig specified does not exist or is not associated with the given account. * INTERNAL: Any non-user error related to technical issues in the backend. In this case, contact Cloud Channel support. Return Value: If successful, the updated ChannelPartnerRepricingConfig resource, otherwise returns an error. Auto-naming is currently not supported for this resource.

Create ChannelPartnerRepricingConfig Resource

new ChannelPartnerRepricingConfig(name: string, args: ChannelPartnerRepricingConfigArgs, opts?: CustomResourceOptions);

@overload
def ChannelPartnerRepricingConfig(resource_name: str,
                                  opts: Optional[ResourceOptions] = None,
                                  account_id: Optional[str] = None,
                                  channel_partner_link_id: Optional[str] = None,
                                  repricing_config: Optional[GoogleCloudChannelV1RepricingConfigArgs] = None)
@overload
def ChannelPartnerRepricingConfig(resource_name: str,
                                  args: ChannelPartnerRepricingConfigArgs,
                                  opts: Optional[ResourceOptions] = None)

func NewChannelPartnerRepricingConfig(ctx *Context, name string, args ChannelPartnerRepricingConfigArgs, opts ...ResourceOption) (*ChannelPartnerRepricingConfig, error)

public ChannelPartnerRepricingConfig(string name, ChannelPartnerRepricingConfigArgs args, CustomResourceOptions? opts = null)

public ChannelPartnerRepricingConfig(String name, ChannelPartnerRepricingConfigArgs args)
public ChannelPartnerRepricingConfig(String name, ChannelPartnerRepricingConfigArgs args, CustomResourceOptions options)

type: google-native:cloudchannel/v1:ChannelPartnerRepricingConfig
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.

name string: The unique name of the resource.
args ChannelPartnerRepricingConfigArgs: The arguments to resource properties.
opts CustomResourceOptions: Bag of options to control resource's behavior.

resource_name str: The unique name of the resource.
args ChannelPartnerRepricingConfigArgs: The arguments to resource properties.
opts ResourceOptions: Bag of options to control resource's behavior.

ctx Context: Context object for the current deployment.
name string: The unique name of the resource.
args ChannelPartnerRepricingConfigArgs: The arguments to resource properties.
opts ResourceOption: Bag of options to control resource's behavior.

name string: The unique name of the resource.
args ChannelPartnerRepricingConfigArgs: The arguments to resource properties.
opts CustomResourceOptions: Bag of options to control resource's behavior.

name String: The unique name of the resource.
args ChannelPartnerRepricingConfigArgs: The arguments to resource properties.
options CustomResourceOptions: Bag of options to control resource's behavior.

ChannelPartnerRepricingConfig Resource Properties

To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.

Inputs

The ChannelPartnerRepricingConfig resource accepts the following input properties:

AccountId string
ChannelPartnerLinkId string
RepricingConfig Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1RepricingConfigArgs: The configuration for bill modifications made by a reseller before sending it to ChannelPartner.

AccountId string
ChannelPartnerLinkId string
RepricingConfig GoogleCloudChannelV1RepricingConfigArgs: The configuration for bill modifications made by a reseller before sending it to ChannelPartner.

accountId String
channelPartnerLinkId String
repricingConfig GoogleCloudChannelV1RepricingConfigArgs: The configuration for bill modifications made by a reseller before sending it to ChannelPartner.

accountId string
channelPartnerLinkId string
repricingConfig GoogleCloudChannelV1RepricingConfigArgs: The configuration for bill modifications made by a reseller before sending it to ChannelPartner.

account_id str
channel_partner_link_id str
repricing_config GoogleCloudChannelV1RepricingConfigArgs: The configuration for bill modifications made by a reseller before sending it to ChannelPartner.

accountId String
channelPartnerLinkId String
repricingConfig Property Map: The configuration for bill modifications made by a reseller before sending it to ChannelPartner.

Outputs

All input properties are implicitly available as output properties. Additionally, the ChannelPartnerRepricingConfig resource produces the following output properties:

Id string: The provider-assigned unique ID for this managed resource.
Name string: Resource name of the ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
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.

Id string: The provider-assigned unique ID for this managed resource.
Name string: Resource name of the ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
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.

id String: The provider-assigned unique ID for this managed resource.
name String: Resource name of the ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
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.

id string: The provider-assigned unique ID for this managed resource.
name string: Resource name of the ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
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.

id str: The provider-assigned unique ID for this managed resource.
name str: Resource name of the ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
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.

id String: The provider-assigned unique ID for this managed resource.
name String: Resource name of the ChannelPartnerRepricingConfig. Format: accounts/{account_id}/channelPartnerLinks/{channel_partner_id}/channelPartnerRepricingConfigs/{id}.
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

GoogleCloudChannelV1ConditionalOverride

Adjustment Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1RepricingAdjustment: Information about the applied override's adjustment.
RebillingBasis Pulumi.GoogleNative.CloudChannel.V1.GoogleCloudChannelV1ConditionalOverrideRebillingBasis: The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
RepricingCondition Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1RepricingCondition: Specifies the condition which, if met, will apply the override.

Adjustment GoogleCloudChannelV1RepricingAdjustment: Information about the applied override's adjustment.
RebillingBasis GoogleCloudChannelV1ConditionalOverrideRebillingBasis: The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
RepricingCondition GoogleCloudChannelV1RepricingCondition: Specifies the condition which, if met, will apply the override.

adjustment GoogleCloudChannelV1RepricingAdjustment: Information about the applied override's adjustment.
rebillingBasis GoogleCloudChannelV1ConditionalOverrideRebillingBasis: The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
repricingCondition GoogleCloudChannelV1RepricingCondition: Specifies the condition which, if met, will apply the override.

adjustment GoogleCloudChannelV1RepricingAdjustment: Information about the applied override's adjustment.
rebillingBasis GoogleCloudChannelV1ConditionalOverrideRebillingBasis: The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
repricingCondition GoogleCloudChannelV1RepricingCondition: Specifies the condition which, if met, will apply the override.

adjustment GoogleCloudChannelV1RepricingAdjustment: Information about the applied override's adjustment.
rebilling_basis GoogleCloudChannelV1ConditionalOverrideRebillingBasis: The RebillingBasis to use for the applied override. Shows the relative cost based on your repricing costs.
repricing_condition GoogleCloudChannelV1RepricingCondition: Specifies the condition which, if met, will apply the override.

adjustment Property Map: Information about the applied override's adjustment.
rebillingBasis "REBILLING_BASIS_UNSPECIFIED" | "COST_AT_LIST" | "DIRECT_CUSTOMER_COST": 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.

GoogleCloudChannelV1ConditionalOverrideRebillingBasis

RebillingBasisUnspecified: REBILLING_BASIS_UNSPECIFIED
Not used.
CostAtList: COST_AT_LIST
Use the list cost, also known as the MSRP.
DirectCustomerCost: DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

GoogleCloudChannelV1ConditionalOverrideRebillingBasisRebillingBasisUnspecified: REBILLING_BASIS_UNSPECIFIED
Not used.
GoogleCloudChannelV1ConditionalOverrideRebillingBasisCostAtList: COST_AT_LIST
Use the list cost, also known as the MSRP.
GoogleCloudChannelV1ConditionalOverrideRebillingBasisDirectCustomerCost: DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

RebillingBasisUnspecified: REBILLING_BASIS_UNSPECIFIED
Not used.
CostAtList: COST_AT_LIST
Use the list cost, also known as the MSRP.
DirectCustomerCost: DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

RebillingBasisUnspecified: REBILLING_BASIS_UNSPECIFIED
Not used.
CostAtList: COST_AT_LIST
Use the list cost, also known as the MSRP.
DirectCustomerCost: DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

REBILLING_BASIS_UNSPECIFIED: REBILLING_BASIS_UNSPECIFIED
Not used.
COST_AT_LIST: COST_AT_LIST
Use the list cost, also known as the MSRP.
DIRECT_CUSTOMER_COST: DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

"REBILLING_BASIS_UNSPECIFIED": REBILLING_BASIS_UNSPECIFIED
Not used.
"COST_AT_LIST": COST_AT_LIST
Use the list cost, also known as the MSRP.
"DIRECT_CUSTOMER_COST": DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

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.

GoogleCloudChannelV1PercentageAdjustment

Percentage Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleTypeDecimal: 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 GoogleTypeDecimal: 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 GoogleTypeDecimal: 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 GoogleTypeDecimal: 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 GoogleTypeDecimal: 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"

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"

GoogleCloudChannelV1RepricingAdjustment

PercentageAdjustment Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1PercentageAdjustment: Flat markup or markdown on an entire bill.

PercentageAdjustment GoogleCloudChannelV1PercentageAdjustment: Flat markup or markdown on an entire bill.

percentageAdjustment GoogleCloudChannelV1PercentageAdjustment: Flat markup or markdown on an entire bill.

percentageAdjustment GoogleCloudChannelV1PercentageAdjustment: Flat markup or markdown on an entire bill.

percentage_adjustment GoogleCloudChannelV1PercentageAdjustment: Flat markup or markdown on an entire bill.

percentageAdjustment Property Map: Flat markup or markdown on an entire bill.

GoogleCloudChannelV1RepricingAdjustmentResponse

PercentageAdjustment Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1PercentageAdjustmentResponse: Flat markup or markdown on an entire bill.

PercentageAdjustment GoogleCloudChannelV1PercentageAdjustmentResponse: Flat markup or markdown on an entire bill.

percentageAdjustment GoogleCloudChannelV1PercentageAdjustmentResponse: Flat markup or markdown on an entire bill.

percentageAdjustment GoogleCloudChannelV1PercentageAdjustmentResponse: Flat markup or markdown on an entire bill.

percentage_adjustment GoogleCloudChannelV1PercentageAdjustmentResponse: Flat markup or markdown on an entire bill.

percentageAdjustment Property Map: Flat markup or markdown on an entire bill.

GoogleCloudChannelV1RepricingCondition

SkuGroupCondition Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1SkuGroupCondition: SKU Group condition for override.

SkuGroupCondition GoogleCloudChannelV1SkuGroupCondition: SKU Group condition for override.

skuGroupCondition GoogleCloudChannelV1SkuGroupCondition: SKU Group condition for override.

skuGroupCondition GoogleCloudChannelV1SkuGroupCondition: SKU Group condition for override.

sku_group_condition GoogleCloudChannelV1SkuGroupCondition: SKU Group condition for override.

skuGroupCondition Property Map: SKU Group condition for override.

GoogleCloudChannelV1RepricingConditionResponse

SkuGroupCondition Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1SkuGroupConditionResponse: SKU Group condition for override.

SkuGroupCondition GoogleCloudChannelV1SkuGroupConditionResponse: SKU Group condition for override.

skuGroupCondition GoogleCloudChannelV1SkuGroupConditionResponse: SKU Group condition for override.

skuGroupCondition GoogleCloudChannelV1SkuGroupConditionResponse: SKU Group condition for override.

sku_group_condition GoogleCloudChannelV1SkuGroupConditionResponse: SKU Group condition for override.

skuGroupCondition Property Map: SKU Group condition for override.

GoogleCloudChannelV1RepricingConfig

Adjustment Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1RepricingAdjustment: Information about the adjustment.
EffectiveInvoiceMonth Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleTypeDate: The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
RebillingBasis Pulumi.GoogleNative.CloudChannel.V1.GoogleCloudChannelV1RepricingConfigRebillingBasis: The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
ChannelPartnerGranularity Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1RepricingConfigChannelPartnerGranularity: Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
ConditionalOverrides List<Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1ConditionalOverride>: 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.
EntitlementGranularity Pulumi.GoogleNative.CloudChannel.V1.Inputs.GoogleCloudChannelV1RepricingConfigEntitlementGranularity: Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

Adjustment GoogleCloudChannelV1RepricingAdjustment: Information about the adjustment.
EffectiveInvoiceMonth GoogleTypeDate: The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
RebillingBasis GoogleCloudChannelV1RepricingConfigRebillingBasis: The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
ChannelPartnerGranularity GoogleCloudChannelV1RepricingConfigChannelPartnerGranularity: Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
ConditionalOverrides []GoogleCloudChannelV1ConditionalOverride: 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.
EntitlementGranularity GoogleCloudChannelV1RepricingConfigEntitlementGranularity: Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

adjustment GoogleCloudChannelV1RepricingAdjustment: Information about the adjustment.
effectiveInvoiceMonth GoogleTypeDate: The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
rebillingBasis GoogleCloudChannelV1RepricingConfigRebillingBasis: The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
channelPartnerGranularity GoogleCloudChannelV1RepricingConfigChannelPartnerGranularity: Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
conditionalOverrides List<GoogleCloudChannelV1ConditionalOverride>: 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.
entitlementGranularity GoogleCloudChannelV1RepricingConfigEntitlementGranularity: Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

adjustment GoogleCloudChannelV1RepricingAdjustment: Information about the adjustment.
effectiveInvoiceMonth GoogleTypeDate: The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
rebillingBasis GoogleCloudChannelV1RepricingConfigRebillingBasis: The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
channelPartnerGranularity GoogleCloudChannelV1RepricingConfigChannelPartnerGranularity: Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
conditionalOverrides GoogleCloudChannelV1ConditionalOverride[]: 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.
entitlementGranularity GoogleCloudChannelV1RepricingConfigEntitlementGranularity: Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

adjustment GoogleCloudChannelV1RepricingAdjustment: Information about the adjustment.
effective_invoice_month GoogleTypeDate: The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
rebilling_basis GoogleCloudChannelV1RepricingConfigRebillingBasis: The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
channel_partner_granularity GoogleCloudChannelV1RepricingConfigChannelPartnerGranularity: Applies the repricing configuration at the channel partner level. This is the only supported value for ChannelPartnerRepricingConfig.
conditional_overrides Sequence[GoogleCloudChannelV1ConditionalOverride]: 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.
entitlement_granularity GoogleCloudChannelV1RepricingConfigEntitlementGranularity: Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

adjustment Property Map: Information about the adjustment.
effectiveInvoiceMonth Property Map: The YearMonth when these adjustments activate. The Day field needs to be "0" since we only accept YearMonth repricing boundaries.
rebillingBasis "REBILLING_BASIS_UNSPECIFIED" | "COST_AT_LIST" | "DIRECT_CUSTOMER_COST": The RebillingBasis to use for this bill. Specifies the relative cost based on repricing costs you will apply.
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.
entitlementGranularity Property Map: Applies the repricing configuration at the entitlement level. This is the only supported value for CustomerRepricingConfig.

GoogleCloudChannelV1RepricingConfigEntitlementGranularity

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}

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}

GoogleCloudChannelV1RepricingConfigRebillingBasis

RebillingBasisUnspecified: REBILLING_BASIS_UNSPECIFIED
Not used.
CostAtList: COST_AT_LIST
Use the list cost, also known as the MSRP.
DirectCustomerCost: DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

GoogleCloudChannelV1RepricingConfigRebillingBasisRebillingBasisUnspecified: REBILLING_BASIS_UNSPECIFIED
Not used.
GoogleCloudChannelV1RepricingConfigRebillingBasisCostAtList: COST_AT_LIST
Use the list cost, also known as the MSRP.
GoogleCloudChannelV1RepricingConfigRebillingBasisDirectCustomerCost: DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

RebillingBasisUnspecified: REBILLING_BASIS_UNSPECIFIED
Not used.
CostAtList: COST_AT_LIST
Use the list cost, also known as the MSRP.
DirectCustomerCost: DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

RebillingBasisUnspecified: REBILLING_BASIS_UNSPECIFIED
Not used.
CostAtList: COST_AT_LIST
Use the list cost, also known as the MSRP.
DirectCustomerCost: DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

REBILLING_BASIS_UNSPECIFIED: REBILLING_BASIS_UNSPECIFIED
Not used.
COST_AT_LIST: COST_AT_LIST
Use the list cost, also known as the MSRP.
DIRECT_CUSTOMER_COST: DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

"REBILLING_BASIS_UNSPECIFIED": REBILLING_BASIS_UNSPECIFIED
Not used.
"COST_AT_LIST": COST_AT_LIST
Use the list cost, also known as the MSRP.
"DIRECT_CUSTOMER_COST": DIRECT_CUSTOMER_COST
Pass through all discounts except the Reseller Program Discount. If this is the default cost base and no adjustments are specified, the output cost will be exactly what the customer would see if they viewed the bill in the Google Cloud Console.

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.

GoogleCloudChannelV1SkuGroupCondition

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

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

GoogleTypeDate

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.

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.

GoogleTypeDecimal

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.

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