google-apis-merchantapi_inventories_v1beta 0.9.0 → 0.11.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 077131facc51ae7ced4e77d81e5e5d9fc208c205650ac4d9dcb7ec5de6f0d5a9
4
- data.tar.gz: bd11c549d960955f3458e224e5da6a8492bc9decac5d2ff00b8f5e4a0d24e760
3
+ metadata.gz: c3e8c52ffb7ca5080270c66af1079ee56928b9eb951c81daa66cd2408b79982e
4
+ data.tar.gz: f8b3053626fe89b26d4a715b846e0b0917926c82a5be9599365a3fe3da772a36
5
5
  SHA512:
6
- metadata.gz: 336bcd24deed6d136bb769d3904bcc391a3bdbd578e29328c5f7e3e574ab53783ddd8e4fcc7edff8ef005496bf2eee689f6ae0e3e9cffe21bb57ffcb97305ac8
7
- data.tar.gz: dd6f15006848957b32802757e67abc67f0add797ca77f4847a365c862cc41d24be0612d705a0255b171c122cce2ef26bd5a921302cd4719679e5fb936de36742
6
+ metadata.gz: 1cf452c440f1e3b68af77abe3c27363c98b914b7f2ec2d88c1d51eca4f0ea687c6cf6dbeb8b539b156d1af1d017bcfc0d262e5edfc03f2000defbb719a7bf9e0
7
+ data.tar.gz: 63ce30a6cdf2eab754009a0504990f8cff15d3a9ddbbec811da14bc2076ab98cd674a6ad2987896cfae7006ea86410a4fd7006f4529e9d8711d4905da8ce4df5
data/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Release history for google-apis-merchantapi_inventories_v1beta
2
2
 
3
+ ### v0.11.0 (2025-11-23)
4
+
5
+ * Regenerated from discovery document revision 20251118
6
+
7
+ ### v0.10.0 (2025-11-16)
8
+
9
+ * Regenerated from discovery document revision 20251109
10
+
3
11
  ### v0.9.0 (2025-06-29)
4
12
 
5
13
  * Regenerated from discovery document revision 20250623
@@ -189,7 +189,32 @@ module Google
189
189
  attr_accessor :instore_product_location
190
190
 
191
191
  # Output only. The name of the `LocalInventory` resource. Format: `accounts/`
192
- # account`/products/`product`/localInventories/`store_code``
192
+ # account`/products/`product`/localInventories/`store_code`` The ``product``
193
+ # segment is a unique identifier for the product. This identifier must be unique
194
+ # within a merchant account and generally follows the structure: `
195
+ # content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy
196
+ # local products, the structure is: `local~content_language~feed_label~offer_id`.
197
+ # Example: `local~en~US~sku123` The format of the ``product`` segment in the
198
+ # URL is automatically detected by the server, supporting two options: 1. **
199
+ # Encoded Format**: The ``product`` segment is an unpadded base64url encoded
200
+ # string (RFC 4648 Section 5). The decoded string must result in the `
201
+ # content_language~feed_label~offer_id` structure. This encoding MUST be used if
202
+ # any part of the product identifier (like `offer_id`) contains characters such
203
+ # as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`
204
+ # for `store_code` "store123", the ``product`` segment must be the base64url
205
+ # encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The full resource name
206
+ # for the local inventory would be `accounts/123/products/ZW5-VVMtc2t1LzEyMw/
207
+ # localInventories/store123`. 2. **Plain Format**: The ``product`` segment is
208
+ # the tilde-separated string `content_language~feed_label~offer_id`. This format
209
+ # is suitable only when `content_language`, `feed_label`, and `offer_id` do not
210
+ # contain URL-problematic characters like `/`, `%`, or `~`. We recommend using
211
+ # the **Encoded Format** for all product IDs to ensure correct parsing,
212
+ # especially those containing special characters. The presence of tilde (`~`)
213
+ # characters in the ``product`` segment is used to differentiate between the two
214
+ # formats. Note: For calls to the v1beta version, the plain format for the
215
+ # product segment is `channel~content_language~feed_label~offer_id`. For example,
216
+ # the full resource name for a local inventory at `store_code` "store123" would
217
+ # be: `accounts/123/products/online~en~US~sku123/localInventories/store123`.
193
218
  # Corresponds to the JSON property `name`
194
219
  # @return [String]
195
220
  attr_accessor :name
@@ -439,9 +464,33 @@ module Google
439
464
  # @return [Array<Google::Apis::MerchantapiInventoriesV1beta::CustomAttribute>]
440
465
  attr_accessor :custom_attributes
441
466
 
442
- # Output only. The name of the `RegionalInventory` resource. Format: ``
443
- # regional_inventory.name=accounts/`account`/products/`product`/
444
- # regionalInventories/`region``
467
+ # Output only. The name of the `RegionalInventory` resource. Format: `accounts/`
468
+ # account`/products/`product`/regionalInventories/`region`` The ``product``
469
+ # segment is a unique identifier for the product. This identifier must be unique
470
+ # within a merchant account and generally follows the structure: `
471
+ # content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy
472
+ # local products, the structure is: `local~content_language~feed_label~offer_id`.
473
+ # Example: `local~en~US~sku123` The format of the ``product`` segment in the
474
+ # URL is automatically detected by the server, supporting two options: 1. **
475
+ # Encoded Format**: The ``product`` segment is an unpadded base64url encoded
476
+ # string (RFC 4648 Section 5). The decoded string must result in the `
477
+ # content_language~feed_label~offer_id` structure. This encoding MUST be used if
478
+ # any part of the product identifier (like `offer_id`) contains characters such
479
+ # as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`
480
+ # for `region` "region123", the ``product`` segment must be the base64url
481
+ # encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The full resource name
482
+ # for the regional inventory would be `accounts/123/products/ZW5-VVMtc2t1LzEyMw/
483
+ # regionalInventories/region123`. 2. **Plain Format**: The ``product`` segment
484
+ # is the tilde-separated string `content_language~feed_label~offer_id`. This
485
+ # format is suitable only when `content_language`, `feed_label`, and `offer_id`
486
+ # do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend
487
+ # using the **Encoded Format** for all product IDs to ensure correct parsing,
488
+ # especially those containing special characters. The presence of tilde (`~`)
489
+ # characters in the ``product`` segment is used to differentiate between the two
490
+ # formats. Note: For calls to the v1beta version, the plain format for the
491
+ # product segment is `channel~content_language~feed_label~offer_id`. For example,
492
+ # the full resource name for a regional inventory in `region` "region123" would
493
+ # be: `accounts/123/products/online~en~US~sku123/regionalInventories/region123`.
445
494
  # Corresponds to the JSON property `name`
446
495
  # @return [String]
447
496
  attr_accessor :name
@@ -16,13 +16,13 @@ module Google
16
16
  module Apis
17
17
  module MerchantapiInventoriesV1beta
18
18
  # Version of the google-apis-merchantapi_inventories_v1beta gem
19
- GEM_VERSION = "0.9.0"
19
+ GEM_VERSION = "0.11.0"
20
20
 
21
21
  # Version of the code generator used to generate this client
22
22
  GENERATOR_VERSION = "0.18.0"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20250623"
25
+ REVISION = "20251118"
26
26
  end
27
27
  end
28
28
  end
@@ -58,6 +58,31 @@ module Google
58
58
  # @param [String] name
59
59
  # Required. The name of the local inventory for the given product to delete.
60
60
  # Format: `accounts/`account`/products/`product`/localInventories/`store_code``
61
+ # The ``product`` segment is a unique identifier for the product. This
62
+ # identifier must be unique within a merchant account and generally follows the
63
+ # structure: `content_language~feed_label~offer_id`. Example: `en~US~sku123` For
64
+ # legacy local products, the structure is: `local~content_language~feed_label~
65
+ # offer_id`. Example: `local~en~US~sku123` The format of the ``product`` segment
66
+ # in the URL is automatically detected by the server, supporting two options: 1.
67
+ # **Encoded Format**: The ``product`` segment is an unpadded base64url encoded
68
+ # string (RFC 4648 Section 5). The decoded string must result in the `
69
+ # content_language~feed_label~offer_id` structure. This encoding MUST be used if
70
+ # any part of the product identifier (like `offer_id`) contains characters such
71
+ # as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`
72
+ # for `store_code` "store123", the ``product`` segment must be the base64url
73
+ # encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The full resource name
74
+ # for the local inventory would be `accounts/123/products/ZW5-VVMtc2t1LzEyMw/
75
+ # localInventories/store123`. 2. **Plain Format**: The ``product`` segment is
76
+ # the tilde-separated string `content_language~feed_label~offer_id`. This format
77
+ # is suitable only when `content_language`, `feed_label`, and `offer_id` do not
78
+ # contain URL-problematic characters like `/`, `%`, or `~`. We recommend using
79
+ # the **Encoded Format** for all product IDs to ensure correct parsing,
80
+ # especially those containing special characters. The presence of tilde (`~`)
81
+ # characters in the ``product`` segment is used to differentiate between the two
82
+ # formats. Note: For calls to the v1beta version, the plain format for the
83
+ # product segment is `channel~content_language~feed_label~offer_id`. For example,
84
+ # the full resource name for a local inventory at `store_code` "store123" would
85
+ # be: `accounts/123/products/online~en~US~sku123/localInventories/store123`.
61
86
  # @param [String] fields
62
87
  # Selector specifying which fields to include in a partial response.
63
88
  # @param [String] quota_user
@@ -91,7 +116,30 @@ module Google
91
116
  # the new or updated `LocalInventory` resource to appear in products.
92
117
  # @param [String] parent
93
118
  # Required. The account and product where this inventory will be inserted.
94
- # Format: `accounts/`account`/products/`product``
119
+ # Format: `accounts/`account`/products/`product`` The ``product`` segment is a
120
+ # unique identifier for the product. This identifier must be unique within a
121
+ # merchant account and generally follows the structure: `content_language~
122
+ # feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the
123
+ # structure is: `local~content_language~feed_label~offer_id`. Example: `local~en~
124
+ # US~sku123` The format of the ``product`` segment in the URL is automatically
125
+ # detected by the server, supporting two options: 1. **Encoded Format**: The ``
126
+ # product`` segment is an unpadded base64url encoded string (RFC 4648 Section 5).
127
+ # The decoded string must result in the `content_language~feed_label~offer_id`
128
+ # structure. This encoding MUST be used if any part of the product identifier (
129
+ # like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To
130
+ # represent the product ID `en~US~sku/123`, the ``product`` segment must be the
131
+ # base64url encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The full
132
+ # resource name for the product would be `accounts/123/products/ZW5-
133
+ # VVMtc2t1LzEyMw`. 2. **Plain Format**: The ``product`` segment is the tilde-
134
+ # separated string `content_language~feed_label~offer_id`. This format is
135
+ # suitable only when `content_language`, `feed_label`, and `offer_id` do not
136
+ # contain URL-problematic characters like `/`, `%`, or `~`. We recommend using
137
+ # the **Encoded Format** for all product IDs to ensure correct parsing,
138
+ # especially those containing special characters. The presence of tilde (`~`)
139
+ # characters in the ``product`` segment is used to differentiate between the two
140
+ # formats. Note: For calls to the v1beta version, the plain format is `channel~
141
+ # content_language~feed_label~offer_id`, for example: `accounts/123/products/
142
+ # online~en~US~sku123`.
95
143
  # @param [Google::Apis::MerchantapiInventoriesV1beta::LocalInventory] local_inventory_object
96
144
  # @param [String] fields
97
145
  # Selector specifying which fields to include in a partial response.
@@ -129,7 +177,30 @@ module Google
129
177
  # given account.
130
178
  # @param [String] parent
131
179
  # Required. The `name` of the parent product to list local inventories for.
132
- # Format: `accounts/`account`/products/`product``
180
+ # Format: `accounts/`account`/products/`product`` The ``product`` segment is a
181
+ # unique identifier for the product. This identifier must be unique within a
182
+ # merchant account and generally follows the structure: `content_language~
183
+ # feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the
184
+ # structure is: `local~content_language~feed_label~offer_id`. Example: `local~en~
185
+ # US~sku123` The format of the ``product`` segment in the URL is automatically
186
+ # detected by the server, supporting two options: 1. **Encoded Format**: The ``
187
+ # product`` segment is an unpadded base64url encoded string (RFC 4648 Section 5).
188
+ # The decoded string must result in the `content_language~feed_label~offer_id`
189
+ # structure. This encoding MUST be used if any part of the product identifier (
190
+ # like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To
191
+ # represent the product ID `en~US~sku/123`, the ``product`` segment must be the
192
+ # base64url encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The full
193
+ # resource name for the product would be `accounts/123/products/ZW5-
194
+ # VVMtc2t1LzEyMw`. 2. **Plain Format**: The ``product`` segment is the tilde-
195
+ # separated string `content_language~feed_label~offer_id`. This format is
196
+ # suitable only when `content_language`, `feed_label`, and `offer_id` do not
197
+ # contain URL-problematic characters like `/`, `%`, or `~`. We recommend using
198
+ # the **Encoded Format** for all product IDs to ensure correct parsing,
199
+ # especially those containing special characters. The presence of tilde (`~`)
200
+ # characters in the ``product`` segment is used to differentiate between the two
201
+ # formats. Note: For calls to the v1beta version, the plain format is `channel~
202
+ # content_language~feed_label~offer_id`, for example: `accounts/123/products/
203
+ # online~en~US~sku123`.
133
204
  # @param [Fixnum] page_size
134
205
  # The maximum number of `LocalInventory` resources for the given product to
135
206
  # return. The service returns fewer than this value if the number of inventories
@@ -177,7 +248,32 @@ module Google
177
248
  # delete response, wait for that period before attempting a delete again.
178
249
  # @param [String] name
179
250
  # Required. The name of the `RegionalInventory` resource to delete. Format: `
180
- # accounts/`account`/products/`product`/regionalInventories/`region``
251
+ # accounts/`account`/products/`product`/regionalInventories/`region`` The ``
252
+ # product`` segment is a unique identifier for the product. This identifier must
253
+ # be unique within a merchant account and generally follows the structure: `
254
+ # content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy
255
+ # local products, the structure is: `local~content_language~feed_label~offer_id`.
256
+ # Example: `local~en~US~sku123` The format of the ``product`` segment in the
257
+ # URL is automatically detected by the server, supporting two options: 1. **
258
+ # Encoded Format**: The ``product`` segment is an unpadded base64url encoded
259
+ # string (RFC 4648 Section 5). The decoded string must result in the `
260
+ # content_language~feed_label~offer_id` structure. This encoding MUST be used if
261
+ # any part of the product identifier (like `offer_id`) contains characters such
262
+ # as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`
263
+ # for `region` "region123", the ``product`` segment must be the base64url
264
+ # encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The full resource name
265
+ # for the regional inventory would be `accounts/123/products/ZW5-VVMtc2t1LzEyMw/
266
+ # regionalInventories/region123`. 2. **Plain Format**: The ``product`` segment
267
+ # is the tilde-separated string `content_language~feed_label~offer_id`. This
268
+ # format is suitable only when `content_language`, `feed_label`, and `offer_id`
269
+ # do not contain URL-problematic characters like `/`, `%`, or `~`. We recommend
270
+ # using the **Encoded Format** for all product IDs to ensure correct parsing,
271
+ # especially those containing special characters. The presence of tilde (`~`)
272
+ # characters in the ``product`` segment is used to differentiate between the two
273
+ # formats. Note: For calls to the v1beta version, the plain format for the
274
+ # product segment is `channel~content_language~feed_label~offer_id`. For example,
275
+ # the full resource name for a regional inventory in `region` "region123" would
276
+ # be: `accounts/123/products/online~en~US~sku123/regionalInventories/region123`.
181
277
  # @param [String] fields
182
278
  # Selector specifying which fields to include in a partial response.
183
279
  # @param [String] quota_user
@@ -211,7 +307,30 @@ module Google
211
307
  # new or updated `RegionalInventory` resource to appear in products.
212
308
  # @param [String] parent
213
309
  # Required. The account and product where this inventory will be inserted.
214
- # Format: `accounts/`account`/products/`product``
310
+ # Format: `accounts/`account`/products/`product`` The ``product`` segment is a
311
+ # unique identifier for the product. This identifier must be unique within a
312
+ # merchant account and generally follows the structure: `content_language~
313
+ # feed_label~offer_id`. Example: `en~US~sku123` For legacy local products, the
314
+ # structure is: `local~content_language~feed_label~offer_id`. Example: `local~en~
315
+ # US~sku123` The format of the ``product`` segment in the URL is automatically
316
+ # detected by the server, supporting two options: 1. **Encoded Format**: The ``
317
+ # product`` segment is an unpadded base64url encoded string (RFC 4648 Section 5).
318
+ # The decoded string must result in the `content_language~feed_label~offer_id`
319
+ # structure. This encoding MUST be used if any part of the product identifier (
320
+ # like `offer_id`) contains characters such as `/`, `%`, or `~`. * Example: To
321
+ # represent the product ID `en~US~sku/123`, the ``product`` segment must be the
322
+ # base64url encoding of this string, which is `ZW5-VVMtc2t1LzEyMw`. The full
323
+ # resource name for the product would be `accounts/123/products/ZW5-
324
+ # VVMtc2t1LzEyMw`. 2. **Plain Format**: The ``product`` segment is the tilde-
325
+ # separated string `content_language~feed_label~offer_id`. This format is
326
+ # suitable only when `content_language`, `feed_label`, and `offer_id` do not
327
+ # contain URL-problematic characters like `/`, `%`, or `~`. We recommend using
328
+ # the **Encoded Format** for all product IDs to ensure correct parsing,
329
+ # especially those containing special characters. The presence of tilde (`~`)
330
+ # characters in the ``product`` segment is used to differentiate between the two
331
+ # formats. Note: For calls to the v1beta version, the plain format is `channel~
332
+ # content_language~feed_label~offer_id`, for example: `accounts/123/products/
333
+ # online~en~US~sku123`.
215
334
  # @param [Google::Apis::MerchantapiInventoriesV1beta::RegionalInventory] regional_inventory_object
216
335
  # @param [String] fields
217
336
  # Selector specifying which fields to include in a partial response.
@@ -249,7 +368,30 @@ module Google
249
368
  # given account.
250
369
  # @param [String] parent
251
370
  # Required. The `name` of the parent product to list `RegionalInventory`
252
- # resources for. Format: `accounts/`account`/products/`product``
371
+ # resources for. Format: `accounts/`account`/products/`product`` The ``product``
372
+ # segment is a unique identifier for the product. This identifier must be unique
373
+ # within a merchant account and generally follows the structure: `
374
+ # content_language~feed_label~offer_id`. Example: `en~US~sku123` For legacy
375
+ # local products, the structure is: `local~content_language~feed_label~offer_id`.
376
+ # Example: `local~en~US~sku123` The format of the ``product`` segment in the
377
+ # URL is automatically detected by the server, supporting two options: 1. **
378
+ # Encoded Format**: The ``product`` segment is an unpadded base64url encoded
379
+ # string (RFC 4648 Section 5). The decoded string must result in the `
380
+ # content_language~feed_label~offer_id` structure. This encoding MUST be used if
381
+ # any part of the product identifier (like `offer_id`) contains characters such
382
+ # as `/`, `%`, or `~`. * Example: To represent the product ID `en~US~sku/123`,
383
+ # the ``product`` segment must be the base64url encoding of this string, which
384
+ # is `ZW5-VVMtc2t1LzEyMw`. The full resource name for the product would be `
385
+ # accounts/123/products/ZW5-VVMtc2t1LzEyMw`. 2. **Plain Format**: The ``product``
386
+ # segment is the tilde-separated string `content_language~feed_label~offer_id`.
387
+ # This format is suitable only when `content_language`, `feed_label`, and `
388
+ # offer_id` do not contain URL-problematic characters like `/`, `%`, or `~`. We
389
+ # recommend using the **Encoded Format** for all product IDs to ensure correct
390
+ # parsing, especially those containing special characters. The presence of tilde
391
+ # (`~`) characters in the ``product`` segment is used to differentiate between
392
+ # the two formats. Note: For calls to the v1beta version, the plain format is `
393
+ # channel~content_language~feed_label~offer_id`, for example: `accounts/123/
394
+ # products/online~en~US~sku123`.
253
395
  # @param [Fixnum] page_size
254
396
  # The maximum number of `RegionalInventory` resources for the given product to
255
397
  # return. The service returns fewer than this value if the number of inventories
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-apis-merchantapi_inventories_v1beta
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.9.0
4
+ version: 0.11.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Google LLC
@@ -57,7 +57,7 @@ licenses:
57
57
  metadata:
58
58
  bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
59
59
  changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-merchantapi_inventories_v1beta/CHANGELOG.md
60
- documentation_uri: https://googleapis.dev/ruby/google-apis-merchantapi_inventories_v1beta/v0.9.0
60
+ documentation_uri: https://googleapis.dev/ruby/google-apis-merchantapi_inventories_v1beta/v0.11.0
61
61
  source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-merchantapi_inventories_v1beta
62
62
  rdoc_options: []
63
63
  require_paths: