@maxim_mazurok/gapi.client.compute-alpha 0.1.20251202 → 0.1.20251210

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.
Files changed (2) hide show
  1. package/index.d.ts +223 -17
  2. package/package.json +1 -1
package/index.d.ts CHANGED
@@ -9,7 +9,7 @@
9
9
  // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
10
10
  // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
11
11
  // Generated from: https://www.googleapis.com/discovery/v1/apis/compute/alpha/rest
12
- // Revision: 20251202
12
+ // Revision: 20251210
13
13
 
14
14
  /// <reference types="gapi.client" />
15
15
 
@@ -4405,6 +4405,194 @@ declare namespace gapi.client {
4405
4405
  */
4406
4406
  queryStringWhitelist?: string[];
4407
4407
  }
4408
+ interface CachePolicy {
4409
+ /**
4410
+ * Bypass the cache when the specified request headers are matched by name,
4411
+ * e.g. Pragma or Authorization headers. Values are case-insensitive. Up to 5
4412
+ * header names can be specified. The cache is bypassed for all
4413
+ * cachePolicy.cacheMode settings.
4414
+ */
4415
+ cacheBypassRequestHeaderNames?: string[];
4416
+ /** The CacheKeyPolicy for this CachePolicy. */
4417
+ cacheKeyPolicy?: CachePolicyCacheKeyPolicy;
4418
+ /**
4419
+ * Specifies the cache setting for all responses from this route.
4420
+ * If not specified, the default value is CACHE_ALL_STATIC.
4421
+ */
4422
+ cacheMode?: string;
4423
+ /**
4424
+ * Specifies a separate client (e.g. browser client) maximum TTL. This is
4425
+ * used to clamp the max-age (or Expires) value sent to the client. With
4426
+ * FORCE_CACHE_ALL, the lesser of client_ttl and default_ttl is used for the
4427
+ * response max-age directive, along with a "public" directive. For
4428
+ * cacheable content in CACHE_ALL_STATIC mode, client_ttl clamps the max-age
4429
+ * from the origin (if specified), or else sets the response max-age
4430
+ * directive to the lesser of the client_ttl and default_ttl, and also
4431
+ * ensures a "public" cache-control directive is present.
4432
+ * If a client TTL is not specified, a default value (1 hour) will be used.
4433
+ * The maximum allowed value is 31,622,400s (1 year).
4434
+ */
4435
+ clientTtl?: Duration;
4436
+ /**
4437
+ * Specifies the default TTL for cached content served by this origin for
4438
+ * responses that do not have an existing valid TTL (max-age or s-maxage).
4439
+ * Setting a TTL of "0" means "always revalidate".
4440
+ * The value of defaultTTL cannot be set to a value greater than that of
4441
+ * maxTTL.
4442
+ * When the cacheMode is set to FORCE_CACHE_ALL, the defaultTTL
4443
+ * will overwrite the TTL set in all responses. The maximum allowed value is
4444
+ * 31,622,400s (1 year). Infrequently accessed objects may be evicted from
4445
+ * the cache before the defined TTL.
4446
+ */
4447
+ defaultTtl?: Duration;
4448
+ /**
4449
+ * Specifies the maximum allowed TTL for cached content served by this
4450
+ * origin.
4451
+ * Cache directives that attempt to set a max-age or s-maxage higher than
4452
+ * this, or an Expires header more than maxTTL seconds in the future will
4453
+ * be capped at the value of maxTTL, as if it were the value of an
4454
+ * s-maxage Cache-Control directive.
4455
+ * Headers sent to the client will not be modified.
4456
+ * Setting a TTL of "0" means "always revalidate".
4457
+ * The maximum allowed value is 31,622,400s (1 year). Infrequently accessed
4458
+ * objects may be evicted from the cache before the defined TTL.
4459
+ */
4460
+ maxTtl?: Duration;
4461
+ /**
4462
+ * Negative caching allows per-status code TTLs to be set, in order
4463
+ * to apply fine-grained caching for common errors or redirects.
4464
+ * This can reduce the load on your origin and improve end-user
4465
+ * experience by reducing response latency.
4466
+ * When the cache mode is set to CACHE_ALL_STATIC or USE_ORIGIN_HEADERS,
4467
+ * negative caching applies to responses with the specified response code
4468
+ * that lack any Cache-Control, Expires, or Pragma: no-cache directives.
4469
+ * When the cache mode is set to FORCE_CACHE_ALL, negative caching applies
4470
+ * to all responses with the specified response code, and override any
4471
+ * caching headers.
4472
+ * By default, Cloud CDN will apply the following default TTLs to these
4473
+ * status codes:
4474
+ * HTTP 300 (Multiple Choice), 301, 308 (Permanent Redirects): 10m
4475
+ * HTTP 404 (Not Found), 410 (Gone),
4476
+ * 451 (Unavailable For Legal Reasons): 120s
4477
+ * HTTP 405 (Method Not Found), 501 (Not Implemented): 60s.
4478
+ * These defaults can be overridden in negative_caching_policy.
4479
+ */
4480
+ negativeCaching?: boolean;
4481
+ /**
4482
+ * Sets a cache TTL for the specified HTTP status code.
4483
+ * negative_caching must be enabled to configure negative_caching_policy.
4484
+ * Omitting the policy and leaving negative_caching enabled will use
4485
+ * Cloud CDN's default cache TTLs.
4486
+ * Note that when specifying an explicit negative_caching_policy, you
4487
+ * should take care to specify a cache TTL for all response codes
4488
+ * that you wish to cache. Cloud CDN will not apply any default
4489
+ * negative caching when a policy exists.
4490
+ */
4491
+ negativeCachingPolicy?: CachePolicyNegativeCachingPolicy[];
4492
+ /**
4493
+ * If true then Cloud CDN will combine multiple concurrent cache fill
4494
+ * requests into a small number of requests to the origin.
4495
+ */
4496
+ requestCoalescing?: boolean;
4497
+ /**
4498
+ * Serve existing content from the cache (if available) when revalidating
4499
+ * content with the origin, or when an error is encountered when refreshing
4500
+ * the cache.
4501
+ * This setting defines the default "max-stale" duration for any cached
4502
+ * responses that do not specify a max-stale directive. Stale responses that
4503
+ * exceed the TTL configured here will not be served. The default limit
4504
+ * (max-stale) is 86400s (1 day), which will allow stale content to be
4505
+ * served up to this limit beyond the max-age (or s-maxage) of a cached
4506
+ * response.
4507
+ * The maximum allowed value is 604800 (1 week).
4508
+ * Set this to zero (0) to disable serve-while-stale.
4509
+ */
4510
+ serveWhileStale?: Duration;
4511
+ }
4512
+ interface CachePolicyCacheKeyPolicy {
4513
+ /**
4514
+ * Names of query string parameters to exclude in cache keys. All other
4515
+ * parameters will be included. Either specify excluded_query_parameters or
4516
+ * included_query_parameters, not both. '&' and '=' will be percent encoded
4517
+ * and not treated as delimiters.
4518
+ *
4519
+ * Note: This field applies to routes that use backend services. Attempting
4520
+ * to set it on a route that points exclusively to Backend Buckets will
4521
+ * result in a configuration error. For routes that point to a Backend
4522
+ * Bucket, use includedQueryParameters to define which parameters should
4523
+ * be a part of the cache key.
4524
+ */
4525
+ excludedQueryParameters?: string[];
4526
+ /**
4527
+ * Allows HTTP cookies (by name) to be used in the cache key.
4528
+ * The name=value pair will be used in the cache key Cloud CDN generates.
4529
+ *
4530
+ * Note: This setting is only applicable to routes that use a Backend
4531
+ * Service. It does not affect requests served by a Backend Bucket.
4532
+ * Attempting to set it on a route that points exclusively to Backend
4533
+ * Buckets will result in a configuration error. Up to 5 cookie names can be
4534
+ * specified.
4535
+ */
4536
+ includedCookieNames?: string[];
4537
+ /** Allows HTTP request headers (by name) to be used in the cache key. */
4538
+ includedHeaderNames?: string[];
4539
+ /**
4540
+ * Names of query string parameters to include in cache keys. All other
4541
+ * parameters will be excluded. Either specify included_query_parameters or
4542
+ * excluded_query_parameters, not both. '&' and '=' will be percent encoded
4543
+ * and not treated as delimiters.
4544
+ */
4545
+ includedQueryParameters?: string[];
4546
+ /**
4547
+ * If true, requests to different hosts will be cached separately.
4548
+ *
4549
+ * Note: This setting is only applicable to routes that use a Backend
4550
+ * Service. It does not affect requests served by a Backend Bucket, as the
4551
+ * host is never included in a Backend Bucket's cache key. Attempting to set
4552
+ * it on a route that points exclusively to Backend Buckets will result in a
4553
+ * configuration error.
4554
+ */
4555
+ includeHost?: boolean;
4556
+ /**
4557
+ * If true, http and https requests will be cached separately.
4558
+ *
4559
+ * Note: This setting is only applicable to routes that use a Backend
4560
+ * Service. It does not affect requests served by a Backend Bucket, as the
4561
+ * protocol is never included in a Backend Bucket's cache key. Attempting to
4562
+ * set on a route that points exclusively to Backend Buckets will result in
4563
+ * a configuration error.
4564
+ */
4565
+ includeProtocol?: boolean;
4566
+ /**
4567
+ * If true, include query string parameters in the cache key according to
4568
+ * included_query_parameters and excluded_query_parameters. If neither is
4569
+ * set, the entire query string will be included. If false, the query string
4570
+ * will be excluded from the cache key entirely.
4571
+ *
4572
+ * Note: This field applies to routes that use backend services. Attempting
4573
+ * to set it on a route that points exclusively to Backend Buckets will
4574
+ * result in a configuration error. For routes that point to a Backend
4575
+ * Bucket, use includedQueryParameters to define which parameters should
4576
+ * be a part of the cache key.
4577
+ */
4578
+ includeQueryString?: boolean;
4579
+ }
4580
+ interface CachePolicyNegativeCachingPolicy {
4581
+ /**
4582
+ * The HTTP status code to define a TTL against. Only HTTP status codes
4583
+ * 300, 301, 302, 307, 308, 404, 405, 410, 421, 451 and 501 can be
4584
+ * specified as values, and you cannot specify a status code more than
4585
+ * once.
4586
+ */
4587
+ code?: number;
4588
+ /**
4589
+ * The TTL (in seconds) for which to cache responses with the
4590
+ * corresponding status code.
4591
+ * The maximum allowed value is 1800s (30 minutes). Infrequently accessed
4592
+ * objects may be evicted from the cache before the defined TTL.
4593
+ */
4594
+ ttl?: Duration;
4595
+ }
4408
4596
  interface CalendarModeAdviceRequest {
4409
4597
  /**
4410
4598
  * Specification of resources to create in the future.
@@ -7996,6 +8184,7 @@ declare namespace gapi.client {
7996
8184
  * address number.
7997
8185
  */
7998
8186
  IPAddress?: string;
8187
+ IPAddresses?: string[];
7999
8188
  /**
8000
8189
  * Resource reference of a PublicDelegatedPrefix. The PDP must
8001
8190
  * be a sub-PDP in EXTERNAL_IPV6_FORWARDING_RULE_CREATION mode.
@@ -9196,17 +9385,21 @@ declare namespace gapi.client {
9196
9385
  }
9197
9386
  interface GlobalVmExtensionPolicyRolloutOperationRolloutInput {
9198
9387
  /**
9199
- * Optional. [Optional] Specifies the behavior of the Rollout if a conflict is
9200
- * detected in a project during a Rollout. It can be one of the following
9201
- * values:
9202
- * 1) empty : don't overwrite the local value if conflict happens. This is
9203
- * the default behavior.
9204
- * 2) "overwrite" : Overwrite the local value with the rollout value.
9205
- * The concept of "conflict" applies to:
9206
- * 1) Insert action. If the zonal policy already exists when Insert
9207
- * happens, it's a conflict.
9208
- * 2) Update action. If the zonal policy was updated out of band by a
9209
- * zonal API, it's a conflict.
9388
+ * Optional. Specifies the behavior of the rollout if a conflict is detected in a
9389
+ * project during a rollout. This only applies to `insert` and `update`
9390
+ * methods.
9391
+ *
9392
+ * A conflict occurs in the following cases:
9393
+ * * `insert` method: If the zonal policy already exists when the insert
9394
+ * happens.
9395
+ * * `update` method: If the zonal policy was modified by a zonal API call
9396
+ * outside of this rollout.
9397
+ *
9398
+ * Possible values are the following:
9399
+ * * `""` (empty string): If a conflict occurs, the local value is not
9400
+ * overwritten. This is the default behavior.
9401
+ * * `"overwrite"`: If a conflict occurs, the local value is overwritten
9402
+ * with the rollout value.
9210
9403
  */
9211
9404
  conflictBehavior?: string;
9212
9405
  /**
@@ -9218,10 +9411,16 @@ declare namespace gapi.client {
9218
9411
  /** Optional. Predefined rollout plan. */
9219
9412
  predefinedRolloutPlan?: string;
9220
9413
  /**
9221
- * Optional. The UUID of the retry action. Only set it if this is a retry
9222
- * for an existing resource. This is for the user re-populate the resource
9223
- * without changes. An error will be returned if the retry_uuid is set but
9224
- * the resource get modified.
9414
+ * Optional. The UUID that identifies a policy rollout retry attempt for update and
9415
+ * delete operations. Set this field only when retrying a rollout for an
9416
+ * existing extension policy.
9417
+ *
9418
+ * * `update` method: Lets you retry policy rollout without changes.
9419
+ * An error occurs if you set retry_uuid but the policy is modified.
9420
+ * * `delete` method: Lets you retry policy deletion rollout if the
9421
+ * previous deletion rollout is not finished and the policy is in the
9422
+ * DELETING state. If you set this field when the policy is not in the
9423
+ * DELETING state, an error occurs.
9225
9424
  */
9226
9425
  retryUuid?: string;
9227
9426
  }
@@ -11534,6 +11733,11 @@ declare namespace gapi.client {
11534
11733
  retryConditions?: string[];
11535
11734
  }
11536
11735
  interface HttpRouteAction {
11736
+ /**
11737
+ * Cache policy for this URL Map’s route. Available only for Global
11738
+ * EXTERNAL_MANAGED load balancer schemes.
11739
+ */
11740
+ cachePolicy?: CachePolicy;
11537
11741
  /**
11538
11742
  * The specification for allowing client-side cross-origin requests. For more
11539
11743
  * information about the W3C recommendation for cross-origin resource sharing
@@ -21299,6 +21503,8 @@ declare namespace gapi.client {
21299
21503
  ipv6Address?: string;
21300
21504
  /** Output only. [Output Only] Type of the resource. Alwayscompute#networkInterface for network interfaces. */
21301
21505
  kind?: string;
21506
+ /** Output only. [Output Only] MAC address assigned to this network interface. */
21507
+ macAddress?: string;
21302
21508
  /**
21303
21509
  * [Output Only] The name of the network interface, which is generated by the
21304
21510
  * server. For a VM, the network interface uses the nicN naming
@@ -34432,7 +34638,7 @@ declare namespace gapi.client {
34432
34638
  * explicitly set, it will not appear in get listings. If not set
34433
34639
  * the default behavior is determined by the org policy, if there is no org
34434
34640
  * policy specified, then it will default to disabled. This field isn't
34435
- * supported if the subnet purpose field is set toREGIONAL_MANAGED_PROXY.
34641
+ * supported if the subnet purpose field is set toREGIONAL_MANAGED_PROXY. It is recommended to uselogConfig.enable field instead.
34436
34642
  */
34437
34643
  enableFlowLogs?: boolean;
34438
34644
  /** Enables Layer2 communication on the subnetwork. */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@maxim_mazurok/gapi.client.compute-alpha",
3
- "version": "0.1.20251202",
3
+ "version": "0.1.20251210",
4
4
  "description": "TypeScript typings for Compute Engine API alpha",
5
5
  "repository": {
6
6
  "type": "git",