Google Cloud SDK version 205.0.0 introduces new flags for Cloud Bigtable, Datastore index management commands, and promotes several Cloud Interconnect and Compute Engine features to GA. A significant security update enhances SSH key validation for Compute Engine metadata. The release also includes extensive Python 2/3 compatibility refactoring, new API clients for Cloud File and Source Repositories, and foundational improvements to Calliope’s argument parsing.

Jump to: Annotated Release Notes | Unannounced Changes 🕵️ | Stats 📊

Breaking Changes

  • Removed explicit Python 2.7 requirement check in the install.sh script, which changes the SDK’s Python version preference and may affect environments relying on its previous strict enforcement.
  • The --admin-enabled flag for Compute Interconnect Attachments is deprecated and hidden. Users should now use --enable-admin instead.
  • The AddTemplateFlag helper for Dataproc workflow templates has been removed, replaced by concept-based resource arguments. Direct callers of this helper function will experience breakage.
  • The AddFunctionNameArg helper utility was removed. Commands using this utility will need to adapt to the new concept-based resource argument parsing.
  • The default value for --message-format in Cloud Source Repositories topic flags has been removed. Commands that relied on ‘json’ being the default might now need to explicitly specify it if the API default is different or no longer implicitly ‘json’.
  • The entire Google Cloud IoT Core v1 API definition, including its client, message definitions, and resource definitions, has been removed from the SDK. This change will prevent any interactions with cloudiot_v1 endpoints via this SDK version.
  • The standard query parameters bearer_token and pp (pretty-print) have been removed from the API definitions of multiple services. If client code explicitly used these parameters, this constitutes a breaking change. This affects: Bigtable Admin (v2), Bio (v1), Category Manager (v1alpha1, v1alpha2), Cloud Billing (v1), Cloud Build (v1), Cloud Debugger (v2), Cloud Error Reporting (v1beta1), and Cloud Functions (v1). The prettyPrint parameter (camelCase) remains available.
  • Removed bearer_token and pp fields from StandardQueryParameters. This may impact clients directly using these parameters for OAuth authentication or pretty-printing.
  • Removed the entire groups resource, including its IAM methods (setIamPolicy, getIamPolicy, testIamPermissions) and all device management functionality (devices.get, devices.patch, devices.delete, devices.modifyCloudToDeviceConfig, devices.configVersions.list, devices.states.list) under the cloudiot.projects.locations.registries.groups hierarchy from the Cloud IoT v1 API. This is a significant breaking change for any automation or tools interacting with device groups.
  • Removed bearer_token and pp fields from StandardQueryParameters in Cloud KMS v1 messages and API definition. This may impact clients directly using these parameters.
  • Removed bearer_token and pp fields from StandardQueryParameters in Cloud Resource Search v1 messages and API definition. This may impact clients directly using these parameters.
  • Removed bearer_token and pp fields from StandardQueryParameters in Cloud Scheduler v1alpha1 messages and API definition. This may impact clients directly using these parameters.
  • Removed bearer_token and pp fields from StandardQueryParameters in Cloud Shell v1 messages and API definition. This may impact clients directly using these parameters.
  • Removed bearer_token and pp fields from StandardQueryParameters in Cloud Shell v1alpha1 messages and API definition. This may impact clients directly using these parameters.
  • Removed bearer_token and pp fields from StandardQueryParameters in Cloud Tasks v2beta2 messages and API definition. This may impact clients directly using these parameters.
  • Removed bearer_token and pp fields from StandardQueryParameters in Cloud Composer v1beta1 messages and API definition. This may impact clients directly using these parameters.
  • In Compute Engine Beta API, the ’type’ enum and field within the NetworkEndpointGroup message have been removed. Previously, only ‘LOAD_BALANCING’ was a valid value for this field.
  • In Compute Engine Beta API, a new NETWORK_ENDPOINT_GROUPS metric has been added to the Quota message’s MetricValueValuesEnum, which has shifted the integer values of subsequent enum members. Code relying on explicit integer values for these enums may be affected.
  • The type field, which specified the type of the network endpoint group (only ‘LOAD_BALANCING’ was valid), has been removed from the NetworkEndpointGroup message.
  • The bearer_token and pp (pretty-print) fields have been removed from the StandardQueryParameters message across multiple APIs (Container, Container Analysis, Dataflow). This affects internal API message structures.
  • The bearer_token and pp (pretty-print) fields have been removed from the StandardQueryParameters message across multiple APIs (Container, Container Analysis, Dataflow). This affects internal API message structures.
  • Removed bearer_token and pp (pretty-print) parameters from StandardQueryParameters in the DLP v2 API. This may affect custom API calls relying on these parameters.
  • Removed bearer_token and pp (pretty-print) parameters from the dlp_v2.json API definition. This may affect clients generated from this definition.
  • The bearer_token and pp (pretty-print) fields have been removed from the StandardQueryParameters across several API versions, including Genomics v1, v1alpha2, v2alpha1, IAM v1, Language v1, Logging v2, ML v1, OS Login v1, and v1alpha. Clients explicitly using these parameters may experience breakage.
  • Removed bearer_token and pp (pretty-print) fields from StandardQueryParameters across multiple APIs. Clients directly using these query parameters for authentication or response formatting might be affected.
  • Removed ‘bearer_token’ and ‘pp’ (pretty-print) standard query parameters from the Video Intelligence v1 API definition and its Python client messages. Clients relying on these specific parameters may be affected.
  • Removed ‘bearer_token’ and ‘pp’ (pretty-print) standard query parameters from the Video Intelligence v1 API definition. Clients relying on these specific parameters may be affected.
  • Removed ‘bearer_token’ and ‘pp’ (pretty-print) standard query parameters from the Vision v1 API definition and its Python client messages. Clients relying on these specific parameters may be affected.
  • Removed ‘bearer_token’ and ‘pp’ (pretty-print) standard query parameters from the Vision v1 API definition. Clients relying on these specific parameters may be affected.
  • Removal of ‘bearer_token’ query parameter from Vision API v1 discovery document. Clients explicitly using this parameter for OAuth bearer token might be affected.
  • Removal of ‘pp’ (pretty-print) query parameter from Vision API v1 discovery document. Clients relying on this specific parameter for response formatting might be affected, though ‘prettyPrint’ remains available.

Security Updates

  • Added validation for SSH keys in Compute Engine metadata to prevent private keys from being uploaded and to ensure public keys adhere to the expected ‘username:key’ format. [MEDIUM]
  • New capabilities to manage signed URL keys for Cloud CDN on Backend Buckets and Backend Services have been introduced, allowing for more granular control over content access and security for CDN-served assets. [MEDIUM]
  • Introduced the Secret message with cipherText and keyName in Genomics v1alpha2 and v2alpha1 APIs. This new message is used by the Action.credentials field to securely specify encrypted credentials for pulling private container images, enhancing credential management. [MEDIUM]

New Features by Service

Cloud Bigtable

  • Added new flags to the cbt command-line tool for specifying a custom User Agent, columns to read, and limiting cells per column.
    • Flags: -user-agent, -columns, -cells-per-column
    • File: arguments.py

Cloud Datastore

  • Added gcloud datastore indexes command group to beta, including cleanup and create commands for managing Datastore indexes.
    • Flags: gcloud datastore indexes cleanup, gcloud datastore indexes create

Cloud Interconnect

  • Promoted interconnects attachments partner related commands to General Availability (GA).

Cloud Storage

  • Updated the gsutil component to version 4.32.

Cloud TPU

  • Added the --preemptible flag to gcloud beta compute tpus create to allow creation of preemptible TPUs.
  • Introduced ’tpu:v1’ API version and removed ’tpu:v1beta1’, with ’tpu:v1alpha1’ becoming the default.
  • The Cloud TPU v1 API has been introduced, providing programmatic access to manage Cloud TPU resources. This includes capabilities to list and retrieve information about accelerator types and supported TensorFlow versions, as well as perform CRUD operations (create, delete, get, list) on TPU nodes. Furthermore, it adds functionality to reimage, reset, start, and stop TPU nodes, and to manage long-running operations associated with these actions.
  • Introduces the Cloud TPU v1 API, providing full lifecycle management for TPU nodes (create, get, list, delete, reimage, reset, stop, start), along with listing available TensorFlow versions and accelerator types.
  • The SDK’s API generation configuration for the Cloud TPU API has been updated to include a ‘v1’ stable version, replacing a previously listed ‘v1beta1’ entry.

Compute Engine

  • Added the --network flag to gcloud compute images export to enable specifying a network other than ‘default’ for the export process.
  • Promoted the --quic-override flag for compute target-https-proxies create and update commands to General Availability (GA).
    • Flags: --quic-override
  • New flags --plan (for commitment duration) and --resources (for VCPU and MEMORY commitments) are added for creating Compute Commitments. A new --type flag is also introduced for commitment types like memory-optimized.
  • New bandwidth options (‘50m’, ‘100m’, ‘200m’, ‘300m’, ‘400m’, ‘500m’, ‘1g’, ‘2g’, ‘5g’, ‘10g’) are available for Interconnect Attachments.
  • Added new fields and methods to support Cloud CDN Signed URLs for Backend Buckets. This includes the BackendBucketCdnPolicy message, the cdnPolicy field in BackendBucket, and addSignedUrlKey/deleteSignedUrlKey methods for backend buckets.
  • Added new fields to support Cloud CDN Signed URLs for Backend Services. This includes signedUrlCacheMaxAgeSec and signedUrlKeyNames in CdnPolicy, and addSignedUrlKey/deleteSignedUrlKey methods for backend services.
  • Introduced DistributionPolicy and DistributionPolicyZoneConfiguration message types in v1, and added a distributionPolicy field to InstanceGroupManager, indicating expanded support for configuring instance distribution in regional managed instance groups.
  • Added a new message type RegionTargetHttpsProxiesSetSslCertificatesRequest to allow setting SSL certificates for regional Target HTTPS Proxies in the alpha API.
  • Added a status field to the NodeGroup message with enum values like CREATING, DELETING, INVALID, and READY in alpha and beta APIs.
  • Added NETWORK_ENDPOINT_GROUPS to the AcceleratorType enum in alpha and beta APIs, indicating support for this resource type.

Dataproc

  • Introduced new resource argument definitions for Dataproc workflow templates, including a completer for regions and standardized project attributes.
  • Added a bootDiskType field to the DiskConfig message, allowing specification of the boot disk type (e.g., pd-ssd, pd-standard) for clusters.

Cloud Functions

  • Introduced concept-based resource arguments for Cloud Functions, enabling more standardized and robust argument parsing for functions and regions.

Cloud Source Repositories

  • Enhanced flexibility for updating Pub/Sub topic configurations, allowing for partial updates to message format or service account without respecifying all fields.
    • Flags: --message-format, --service-account
    • File: util.py:165

IAM

  • Groundwork laid for new add-iam-policy-binding commands through the YAML command framework. This includes new command type ADD_IAM_POLICY_BINDING and logic to fetch, modify, and set IAM policies.

App Engine

  • Introduced a new ‘rolloutStrategy’ field to EndpointsApiService to specify how Endpoints service configurations are managed (FIXED or MANAGED).

Cloud Filestore (possible)

  • Added new API definitions for ‘file’ service (v1alpha1 and v1beta1), indicating support for a new file storage service.

Compute Engine (Alpha)

  • Added new service for managing regional SSL certificates, including operations to delete, get, insert, list, and test IAM permissions for these certificates.
  • Introduced a new service for managing regional Target HTTPS Proxies, supporting delete, get, insert, list, set SSL certificates, set URL maps, and test IAM permissions.
  • Added the GetNatMappingInfo method to the RoutersService to retrieve runtime NAT mapping information of VM endpoints.
  • Added the AggregatedList method to the global SslCertificatesService to retrieve a consolidated list of all regional and global SSL certificate resources.
  • Added the AggregatedList method to the global TargetHttpsProxiesService to retrieve a consolidated list of all regional and global Target HTTPS Proxy resources.
  • Added API request messages for full CRUD (Create, Read, Update, Delete) operations and IAM test permissions for regional SSL Certificates.
  • Introduced resource collections for regional SSL Certificates and regional Target HTTPS Proxies, indicating support for these resources.

Compute Engine (Beta)

  • Added status field and StatusValueValuesEnum to NodeGroupNode for tracking the operational status (CREATING, DELETING, INVALID, READY) of individual nodes within a node group.

Compute Engine (v1)

  • New methods AddSignedUrlKey and DeleteSignedUrlKey added to Backend Buckets for managing Cloud CDN Signed URL Keys.
  • New methods AddSignedUrlKey and DeleteSignedUrlKey added to Backend Services for managing Cloud CDN Signed URL Keys.
  • Added cdnPolicy field to BackendBucket and introduced BackendBucketCdnPolicy to configure signed URL caching and list configured key names.
  • Extended BackendServiceCdnPolicy with signedUrlCacheMaxAgeSec and signedUrlKeyNames for configuring signed URL caching and managing keys for Cloud CDN.
  • Introduced DistributionPolicy and DistributionPolicyZoneConfiguration messages and added distributionPolicy field to InstanceGroupManager, enabling specified instance distribution in regional managed instance groups.

Container Analysis

Cloud Filestore

  • Initial integration of the Cloud Filestore API into the SDK. This chunk introduces the v1alpha1 message definitions and resource structures, along with the v1beta1 API client.
  • Groundwork for the Cloud Filestore service by introducing its v1beta1 API messages and resource definitions. This enables future SDK functionality for managing Filestore instances, locations, and long-running operations.
  • Introduction of the Cloud Filestore API (v1alpha1), enabling programmatic creation, retrieval, updating, and deletion of Filestore instances, volumes, and network configurations. It defines operations for listing locations and managing long-running operations related to Filestore resources.
  • A new API version, file:v1beta1, for Cloud Filestore has been introduced, allowing for the creation and management of cloud file servers via API.

Cloud Life Sciences (Genomics)

  • The Genomics v1alpha2 and v2alpha1 APIs now support specifying a subnetwork for VM network configurations within pipeline resources.
  • The Genomics v1alpha2 and v2alpha1 APIs now allow specifying encrypted credentials (Secret) within an Action to pull container images from private registries.

Cloud Speech-to-Text API

  • Added biasingStrength field with enum options (BIASING_STRENGTH_UNSPECIFIED, LOW, MEDIUM, HIGH) to SpeechContext, enabling more granular control over speech recognition hints for v1 and v1p1beta1.

Cloud SQL Admin API

  • The DemoteMaster functionality is now described as demoting a standalone instance to a Cloud SQL read replica for an external database server, indicating activated or clarified functionality.

TPU

  • Introduction of the Google Cloud TPU v1 API definitions. This includes new message types for managing Accelerator Types, TensorFlow Versions, Nodes (create, delete, get, list, reimage, reset, start, stop), and long-running operations. A key addition is the SchedulingConfig within the Node message, which contains a preemptible boolean field, enabling support for preemptible TPU instances.

Cloud TPU (Alpha)

  • Adds ‘schedulingConfig’ to the TPU Node schema in the v1alpha1 API, allowing configuration for preemptible TPU nodes.

Cloud Filestore (inferred)

  • The SDK’s API generation configuration now includes a ‘file’ API with ‘v1alpha1’ (default) and ‘v1beta1’ versions, indicating new support for a file storage service.

Credential & Auth Changes

  • Implemented new validation logic within metadata_utils.py to check the format of SSH keys and prevent private keys from being added to Compute Engine instance metadata.
  • The bearer_token query parameter, previously used for OAuth bearer tokens, has been removed from StandardQueryParameters across multiple API versions, including Cloud IoT v1, Cloud KMS v1, Cloud Resource Search v1, Cloud Scheduler v1alpha1, Cloud Shell v1 and v1alpha1, Cloud Tasks v2beta2, and Cloud Composer v1beta1. Clients should rely on access_token or standard OAuth 2.0 practices.
  • A new SignedUrlKey message has been added, which includes keyName and keyValue fields, for managing signing keys used in Cloud CDN Signed URLs.
  • In Genomics v1alpha2 and v2alpha1 APIs, the Action message now includes a credentials field which uses the new Secret type for securely providing encrypted credentials for private container image access. The description for the ENABLE_IMAGE_STREAMING flag has also been updated to reflect this new credential handling mechanism.
  • Removed the bearer_token field from StandardQueryParameters across multiple APIs (OS Login, Pub/Sub, Runtime Config, Service Management, Service Networking, Service User, Source Repository, Spanner, Speech-to-Text, Testing). Authentication should rely on the standard Authorization header.
  • The ‘bearer_token’ query parameter has been removed from the Vision API v1 discovery document, potentially indicating a shift in how authentication tokens are handled for this API.

API Changes

Compute Engine

  • Refactored the internal API method for setting security policies on backend services, including making MakeSetSecurityPolicyRequestTuple public.
  • Introduced a new GA-specific patch request method (_MakePatchRequestTupleGa) and re-organized patch logic for interconnect attachments, supporting their promotion to GA.
  • Updated API definitions for compute_alpha, compute_beta, and compute_v1 versions, with notable schema changes in compute_alpha.json.
  • API revisions updated from ‘20180525’ to ‘20180604’ for alpha, beta, and v1 APIs.
  • Clarified descriptions for fingerprint fields in several resources (BackendService, InstanceGroupManager, Metadata, SslPolicy, Subnetwork, UrlMap) to suggest a get() request for the latest fingerprint.
  • The ManagedInstance resource description was updated for clarity from ‘Next available tag: 12’ to ‘A Managed Instance resource’.
  • An output-only region field was added to the SslCertificate message in the alpha API.

Cloud Functions

  • Modified the CreateFunction method to explicitly accept a location argument, changing its call signature and internal resource resolution.

Cloud IoT

  • Restructured the cloudiot_v1 API client, involving the removal of client and resource-specific Python files and updates to message definitions.
  • The groups resource and all its associated methods and device management capabilities under cloudiot.projects.locations.registries.groups have been removed from the Cloud IoT v1 API definition.

Cloud TPU

  • The Cloud TPU API version has been promoted from v1alpha1 to v1 in resource definitions.
  • Introduction of the Cloud TPU v1 API, including new resource definitions (e.g., Projects, Locations, AcceleratorTypes, Nodes, Operations, TensorFlowVersions) and a generated client library to interact with these resources.
  • The TPU API configuration has been updated to support a new ‘v1’ version.

Internal SDK API

  • The CreateRequest method in DeclarativeArgumentGenerator now accepts an override_method parameter, allowing commands to specify a different API method for request creation, useful for operations involving multiple API calls or specialized handling.

Cloud Source Repositories

  • The internal helper CreateTopicResourcePresentationSpec was modified to explicitly take help_text as an argument, changing its internal API.

Multiple APIs (e.g., Access Context Manager, API Keys, App Engine, Bigtable Admin, etc.)

  • Removed ‘bearer_token’ and ‘pp’ (pretty-print) fields from ‘StandardQueryParameters’ across numerous API definitions. This is unlikely to affect gcloud CLI users directly, as these are typically handled internally by the SDK.

App Engine

Bigtable Cluster Admin

  • The API revision for bigtableclusteradmin_v1 has been rolled back from 20180514 to 20180509, indicating a minor correction in the API definition.

Multiple APIs

  • Removed the bearer_token and pp (pretty-print) fields from the StandardQueryParameters object across various APIs including Cloud KMS, Cloud Resource Search, Cloud Scheduler, Cloud Shell, Cloud Tasks, and Cloud Composer.

Compute Engine (Alpha)

  • New Compute Alpha API methods for regional SSL certificate management: compute.regionSslCertificates.delete, compute.regionSslCertificates.get, compute.regionSslCertificates.insert, compute.regionSslCertificates.list, compute.regionSslCertificates.testIamPermissions.
  • New Compute Alpha API methods for regional Target HTTPS Proxy management: compute.regionTargetHttpsProxies.delete, compute.regionTargetHttpsProxies.get, compute.regionTargetHttpsProxies.insert, compute.regionTargetHttpsProxies.list, compute.regionTargetHttpsProxies.setSslCertificates, compute.regionTargetHttpsProxies.setUrlMap, compute.regionTargetHttpsProxies.testIamPermissions.
  • New Compute Alpha API method compute.routers.getNatMappingInfo for retrieving router NAT mapping information.
  • New Compute Alpha API method compute.sslCertificates.aggregatedList for listing all SSL certificates.
  • New Compute Alpha API method compute.targetHttpsProxies.aggregatedList for listing all Target HTTPS Proxies.
  • New API request messages for regional SSL Certificates and related resource collection definitions were added.

Compute Engine (Beta)

Compute Engine (v1)

  • Client methods AddSignedUrlKey and DeleteSignedUrlKey were added for both Backend Buckets and Backend Services.
  • The BackendBucket message now includes cdnPolicy and a new BackendBucketCdnPolicy message defines CDN configurations including signed URL cache settings.
  • The BackendServiceCdnPolicy message now includes signedUrlCacheMaxAgeSec and signedUrlKeyNames fields.
  • New messages DistributionPolicy and DistributionPolicyZoneConfiguration were added and integrated into the InstanceGroupManager message.

Kubernetes Engine

Dataflow

Deployment Manager

  • A minor descriptive change for the type field in DeploymentmanagerTypeProvidersGetTypeRequest from ‘The name of the type provider for this request.’ to ‘The name of the type provider type for this request.’.
  • Clarified the description for the type parameter in DeploymentmanagerTypeProvidersGetTypeRequest (v2beta, alpha, and v2 APIs), changing ’type provider’ to ’type provider type’.
  • Updated API revisions for Deployment Manager Alpha, v2, and v2beta to ‘20180604’.

Discovery API

  • Updated the batchPath for the Discovery v1 API from ‘batch’ to ‘batch/discovery/v1’.

Cloud DLP

  • Refactored descriptions for GooglePrivacyDlpV2DeltaPresenceEstimationConfig, GooglePrivacyDlpV2DeltaPresenceEstimationQuasiIdValues, and GooglePrivacyDlpV2DeltaPresenceEstimationResult for improved readability.
  • Corrected string literals and clarified descriptions for lowerBound and upperBound in GooglePrivacyDlpV2FixedSizeBucketingConfig.
  • Minor wording change in the description for GooglePrivacyDlpV2HotwordRule.
  • Clarified redactAllText in GooglePrivacyDlpV2ImageRedactionConfig to state ‘Only one should be provided’.
  • Clarified the behavior of an empty infoTypes list in GooglePrivacyDlpV2InfoTypeTransformation, stating it applies to all requested infoTypes in InspectConfig.
  • Significantly clarified the OutputSchemaValueValuesEnum, outputSchema field, and table field descriptions for GooglePrivacyDlpV2OutputStorageConfig, detailing usage for Inspect vs. Risk jobs and column handling.
  • Refined the description for GooglePrivacyDlpV2RedactImageRequest to specifically mention image redaction by covering content with a colored rectangle.
  • Extended GooglePrivacyDlpV2SaveFindings compatibility to include ‘Risk’ jobs, in addition to ‘Inspect’.

Cloud DNS

  • Updated API revisions for DNS v1, v1alpha2, v1beta1, v1beta2, and v2beta1 APIs to ‘20180604’.

Cloud Filestore

  • Added new message definitions for Cloud Filestore v1alpha1, including core resources like Instance, NetworkConfig, VolumeConfig, Operation, and Location with their respective fields and enums.
  • Added resource collection definitions for Cloud Filestore v1alpha1, mapping API paths for projects, locations, instances, and operations.
  • Added the API client for Cloud Filestore v1beta1, providing methods to interact with operations (Cancel, Delete, Get, List) and locations (Get, List).
  • Introduced the v1beta1 API for Cloud Filestore, defining message structures for operations (e.g., CancelOperationRequest, Operation), locations (e.g., Location, FileProjectsLocationsGetRequest), and standard error handling (Status).
  • Addition of the file:v1alpha1 Discovery API definition for Cloud Filestore, including schemas for Instance, VolumeConfig, NetworkConfig, Location, and Operation resources, along with methods for listing and managing these resources.

Multiple APIs (Genomics, IAM, Language, Logging, ML, OS Login)

  • The bearer_token and pp fields have been removed from the StandardQueryParameters message across various APIs.

Cloud Life Sciences (Genomics)

  • In Genomics v1alpha2 and v2alpha1, the PipelineResources.Network message now includes a subnetwork field. The Action message has gained a credentials field of the new Secret type.

OS Login API

  • Removed bearer_token and pp from StandardQueryParameters in v1, v1alpha, and v1beta API message and JSON definitions.

Cloud Pub/Sub API

Cloud Runtime Config API

Service Management API

  • Removed bearer_token and pp from StandardQueryParameters in v1 API message and JSON definitions. Also included minor cosmetic changes to string quotes in descriptions.

Service Networking API

  • Removed bearer_token and pp from StandardQueryParameters in v1alpha API message and JSON definitions. Also included minor cosmetic changes to string quotes in descriptions.

Service User API

  • Removed bearer_token and pp from StandardQueryParameters in v1 API message and JSON definitions. Also included minor cosmetic changes to string quotes in descriptions.

Cloud Source Repositories API

Cloud Spanner API

Cloud Speech-to-Text API

  • Added biasingStrength to SpeechContext in v1 and v1p1beta1 API message and JSON definitions. Removed bearer_token and pp from StandardQueryParameters.

Cloud SQL Admin API

  • Updated the description for the AddServerCa method and the DemoteMaster method in v1beta4. Added a new privateNetwork string field to IpConfiguration in v1beta4, marked as ‘Reserved for future use’.

Cloud Storage API

  • Minor cosmetic changes to string quotes in descriptions for Policy members, roles, and TestIamPermissionsResponse permissions.

Cloud Testing API

  • Removed bearer_token and pp from StandardQueryParameters in v1 API message and JSON definitions. Also included minor cosmetic changes to string quotes in descriptions.

TPU

  • The Node message in the tpu.v1alpha1 API was updated to include a new schedulingConfig field and the associated SchedulingConfig message, which allows for specifying preemptible TPUs. This required re-indexing of existing fields (serviceAccount, state, tensorflowVersion).

Cloud TPU (Alpha)

  • The ‘Node’ schema in the TPU v1alpha1 API now includes a ‘schedulingConfig’ field, which contains a ‘preemptible’ boolean field to specify preemptible TPU nodes.

Video Intelligence API

  • Removed ‘bearer_token’ and ‘pp’ (pretty-print) standard query parameters from the API definition and its Python messages, consolidating pretty-print functionality under ‘prettyPrint’.
  • Removed ‘bearer_token’ and ‘pp’ standard query parameters from the v1 API definition.

Vision API

  • Updated the description for ‘bestGuessLabels’ in ‘GoogleCloudVisionV1p2beta1WebDetection’ and ‘WebDetection’ schemas for clarity. Also removed ‘bearer_token’ and ‘pp’ standard query parameters from Python client messages.
  • Removed ‘bearer_token’ and ‘pp’ standard query parameters from the v1 API definition.

Cloud Vision API

  • The description for ‘bestGuessLabels’ in the Vision API v1 discovery document has been updated for clarity, specifying that it infers the topic from similar images on the open web.

Unannounced Changes

Changes found in code but not mentioned in official release notes: 🕵️

Groundwork

  • Enhanced Python runtime detection in install.sh to prefer unversioned python and python3 if python2 is not found, indicating broader Python 3 compatibility efforts.
  • Introduced a new sourcerepo.py API client layer for Google Cloud Source Repositories, enabling new programmatic interactions with source control.
  • Introduced _allow_py3 attribute and DisallowPython3 decorator in Calliope’s base classes, along with Python 3 compatibility checks, allowing command groups to explicitly opt out of Python 3 support.
  • Added a new module calliope/concepts/multitype.py for handling multiple types of concepts, suggesting new advanced argument parsing capabilities.
  • Introduced new Google Cloud File API clients, messages, and discovery documents for v1alpha1 and v1beta1, laying groundwork for managing file storage services.
  • Added new Google Cloud TPU API client, messages, and discovery documents for v1, providing a robust API layer for TPU resource management, complementing the announced --preemptible flag.
  • Introduced FullySpecifiedAnchorFallthrough and FilteredDeps classes in the concepts dependency management, allowing for more granular control and filtering of resource attribute fallthroughs.
  • A new snapshot resource definition has been added to compute/resources.yaml, laying groundwork for new snapshot management commands.
  • Introduced googlecloudsdk/command_lib/projects/resource_args.py to centralize the definition and fallback logic for the project resource attribute across various services, replacing individual ProjectAttributeConfig definitions.
  • Introduced conditional import of the gRPC library, indicating current Python 3 incompatibility for gRPC features and preventing crashes.
  • Added an API endpoint override property for ‘binaryauthorization’, laying groundwork for future features related to this service.
  • New API request messages (ComputeRegionSslCertificatesDeleteRequest, GetRequest, InsertRequest, ListRequest, TestIamPermissionsRequest) were added for regional SSL Certificates in Compute Alpha.
  • Added resource collections for REGIONSSLCERTIFICATES and REGIONTARGETHTTPSPROXIES in Compute Alpha resources.
  • Added StatusValueValuesEnum and a status field to NodeGroupNode in Compute Beta for node status tracking.
  • Added NETWORK_ENDPOINT_GROUPS to the MetricValueValuesEnum within the Quota message in Compute Beta, expanding available quota metrics.
  • New client methods (AddSignedUrlKey, DeleteSignedUrlKey) were introduced for backendBuckets and backendServices in Compute v1.
  • The BackendBucket message was updated to include a cdnPolicy field, alongside the new BackendBucketCdnPolicy message for CDN configuration, including signed URL cache settings.
  • The BackendServiceCdnPolicy message was extended with signedUrlCacheMaxAgeSec and signedUrlKeyNames fields for more detailed CDN signed URL configuration.
  • New API request messages (ComputeBackendBucketsAddSignedUrlKeyRequest, DeleteSignedUrlKeyRequest, ComputeBackendServicesAddSignedUrlKeyRequest, DeleteSignedUrlKeyRequest) were added for managing signed URL keys.
  • New messages DistributionPolicy and DistributionPolicyZoneConfiguration were added to Compute v1, along with the distributionPolicy field in InstanceGroupManager, indicating support for regional instance group distribution policies.
  • A new SignedUrlKey message was added, defining the structure for signed URL keys with keyName and keyValue fields.
  • Added SslCertificateAggregatedList message in compute_alpha.json, likely groundwork for a feature to list SSL certificates across scopes.
  • Added new package structure and client library for a new ‘Cloud File’ service (v1alpha1), including services for instances, operations, and locations. This suggests the introduction or groundwork for a new managed file storage product (e.g., Filestore).
  • Groundwork for the Cloud Filestore API by adding Python message definitions for v1alpha1. This lays the foundation for managing Cloud Filestore resources.
  • Groundwork for the Cloud Filestore API by adding resource definitions for v1alpha1. This defines the structure for API resource names and collections.
  • Groundwork for the Cloud Filestore API by adding the Python API client for v1beta1, enabling programmatic interaction with the service.
  • Addition of v1beta1 API messages for Google Cloud Filestore, including definitions for operations, locations, and common API parameters and error statuses.
  • Addition of resource definitions and base URLs for the v1beta1 Google Cloud Filestore API, setting up resource paths for projects, locations, and operations.
  • Introduction of the file:v1beta1 API discovery document for Cloud Filestore, including its full API surface definition.
  • Addition of Action.credentials field and Secret message in Genomics v1alpha2 and v2alpha1 APIs for encrypted private image credentials, along with the new Network.subnetwork field.
  • Introduced a new package marker file for the TPU v1 API, signifying groundwork for a new API version.
  • Added privateNetwork string field to Cloud SQL Admin’s IpConfiguration in v1beta4, marked as ‘Reserved for future use’, indicating future feature development.
  • New resource definitions for the Cloud TPU v1 API were added, outlining the structure for projects, locations, accelerator types, nodes, operations, and TensorFlow versions.
  • Added new API client and message definitions for the Google Cloud TPU v1 API, which represents a stable API version.
  • Configuration added for a new ‘file’ API with ‘v1alpha1’ and ‘v1beta1’ versions, suggesting groundwork for Cloud Filestore or a similar service.
  • The TPU API configuration was updated to promote or introduce a ‘v1’ version, replacing a ‘v1beta1’ entry in the API generation config.

Refactoring

  • Widespread addition of from __future__ import unicode_literals and adjustments to string/bytes handling across numerous Python files, indicating a large-scale refactoring for Python 2/3 compatibility.
  • Deletion of several __init__.py files in api_lib/util, calliope/concepts, and various core subdirectories, likely part of Python packaging refactoring or preparation for Python 3.
  • Added __hash__ methods to several Calliope ConceptSpec and Attribute classes, likely for performance improvements in data structures like sets or dictionaries.
  • Significant refactoring of concept dependency handling logic within calliope/concepts/deps.py, indicating internal improvements to argument resolution.
  • Major rewrite of googlecloudsdk/core/util/platforms.py, enhancing platform utility functions, potentially related to improved Python version detection and environment setup.
  • Removed the google-cloud-sdk/lib/googlecloudsdk/command_lib/app/__init__.py file, suggesting internal restructuring within the app command group.
  • Several App Engine command utility files (e.g., browser_dispatcher.py, create_util.py) had from __future__ import unicode_literals added, indicating Python 2/3 compatibility adjustments.
  • The trigger_build_server_side property in app/deploy_util.py now uses .GetBool() for retrieving boolean values, improving property handling.
  • Consolidated project attribute configuration across several services (Bigtable, Category Manager, Composer, Binary Authorization, DNS) by replacing specific ProjectAttributeConfig definitions with a common project_resource_args.PROJECT_ATTRIBUTE_CONFIG.
  • Clarified the help text for the --replacement-disk flag for Compute Images, noting that the value is purely informational and not validated.
  • Significant refactoring in compute/tpus/util.py, including the removal of custom API interaction functions (e.g., Describe, Delete, Create) in favor of a more generic API client (apis.GetMessagesModule), aligning with the TPU API v1 promotion.
  • Extensive refactoring for Python 2/3 compatibility, including adding absolute_import and unicode_literals to many files, converting range to list(range), and using six.text_type for string conversions.
  • Deletion of empty package marker files google-cloud-sdk/lib/googlecloudsdk/command_lib/pubsub/__init__.py, google-cloud-sdk/lib/googlecloudsdk/command_lib/util/apis/__init__.py, and google-cloud-sdk/lib/googlecloudsdk/command_lib/util/args/__init__.py.
  • Clarified help text for --authorized-gae-apps, --authorized-networks, and --database-flags in Cloud SQL to explicitly state that values replace existing lists during updates.
  • Improved handling of base64 encoded data for Pub/Sub messages in Cloud Scheduler by ensuring proper unicode conversion before JSON serialization.
  • Various minor wording and formatting improvements in help texts and error messages across several services (IAM, KMS, Monitoring, Spanner, Scheduler).
  • Refactoring of CLI tree generation and cache utilities for improved robustness and Python 2/3 compatibility, including changes to file I/O using io.open and error handling.
  • Correction in static completion output to ensure proper encoding when writing to the completion stream, and added a robustness check for closing the file object.
  • Improved help text generation for ‘–labels’ and ‘–update-labels’ flags by introducing more descriptive format help messages for keys and values.
  • Refactored Python package structure by removing content from numerous __init__.py files across command_lib/util/concepts, command_lib/util/hooks, core, and third_party directories, potentially indicating a move to implicit namespace packages.
  • Enhanced resource completer logic to consider API versions when retrieving collection information for attributes.
  • Improved resource parsing and dependency resolution for complex resource arguments by adding anchor-based fallthroughs and refining fallthrough value handling.
  • Modified SSH command utility to support more flexible output handling, allowing stdout to be piped to a specific file or written to the console log.
  • Cleaned up pytype annotations in metadata_table.py and persistent_cache_base.py for improved type checking.
  • Updated Python 2 unicode string literals to be compatible with Python 3.
  • Enhanced GCE metadata server response decoding by explicitly using http_encoding.Decode for robustness.
  • Implemented Python 3 compatibility fix for map function, explicitly converting its iterator output to a list.
  • Improved datetime parsing flexibility in resource expressions to accommodate either ‘T’ or a space as separators.
  • Enhanced YAML printer to correctly represent collections.OrderedDict objects, preserving insertion order in YAML output.
  • Improved error message for AmbiguousResourcePath by providing more specific collection information.
  • Corrected the suggested command for re-running installation to use ‘gcloud’ instead of the interpreter path, improving user instructions.
  • Updated Python version compatibility checks to provide more tailored messages for Python 2.x and 3.x, and introduced an option to raise an exception instead of exiting.
  • A typo in the description for the OFFLINE status of CloudFunction messages was corrected, changing isn’t to isn't.
  • Minor cosmetic cleanup in Cloud Resource Manager v1 messages, replacing unicode left/right double quotation marks (“, ”) with standard ASCII double quotation marks (").
  • Minor cosmetic cleanup in Cloud Resource Manager v2alpha1 messages, replacing unicode apostrophe (’) with standard ASCII single quotation mark (') in Folder resource descriptions for displayName and parent fields.
  • Minor cosmetic cleanup in Cloud Resource Manager v2beta1 messages, replacing unicode apostrophe (’) with standard ASCII single quotation mark (') in Folder resource descriptions for displayName and parent fields.
  • Improved documentation/description for fingerprint fields in several Compute Alpha, Beta, and v1 messages (e.g., BackendService, InstanceGroupManager, Metadata, SslPolicy, Subnetwork, TargetVpnGateway, UrlMap).
  • Description updates for DistributionPolicy and DistributionPolicyZoneConfiguration in Compute Beta.
  • The description for ManagedInstance was changed from ‘Next available tag: 12’ to ‘A Managed Instance resource.’ in Compute Beta and v1.
  • Removed bearer_token and pp fields from StandardQueryParameters messages across Container, Container Analysis, and Dataflow APIs, indicating internal API refactoring.
  • Minor description updates for various fields across Compute Engine and Deployment Manager APIs, improving clarity without adding new functionality.
  • Removal of bearer_token and pp (pretty-print) from StandardQueryParameters across various APIs (Genomics, IAM, Language, Logging, ML, OS Login). This appears to be an internal cleanup/refactoring of common API parameters.
  • Minor text changes in Genomics v1alpha2 and v2alpha1 API descriptions, such as replacing ‘NVIDIA\xae Tesla\xae’ with ‘NVIDIA(R) Tesla(R)’ for accelerator types.
  • API revision updates for replicapoolupdater_v1beta1.json, sqladmin_v1beta3.json, sqladmin_v1beta4.json, storage_v1.json, and toolresults_v1beta3.json indicating general regeneration or minor updates to API definitions.
  • Minor cosmetic changes to string quotes in API message and JSON descriptions across Service Management, Service Networking, Service Usage, Service User, Storage, and Testing APIs.
  • Updated tpu.v1alpha1 API message definitions to include SchedulingConfig for Node resources, aligning with features introduced in the tpu.v1 API.
  • Removal of redundant ‘bearer_token’ and ‘pp’ standard query parameters from Video Intelligence v1 API client messages and API definition.
  • Removal of redundant ‘bearer_token’ and ‘pp’ standard query parameters from Video Intelligence v1 API definition.
  • Removal of redundant ‘bearer_token’ and ‘pp’ standard query parameters from Vision v1 API client messages and API definition. Also a minor description update.
  • Removal of redundant ‘bearer_token’ and ‘pp’ standard query parameters from Vision v1 API definition.
  • Removed ‘bearer_token’ query parameter from Vision API v1 discovery document.
  • Removed ‘pp’ (pretty-print) query parameter from Vision API v1 discovery document.
  • Clarified description for ‘bestGuessLabels’ field in Vision API v1 discovery document.

Hidden Feature

  • Added new fine-grained bandwidth options (‘50m’, ‘100m’, ‘200m’, ‘300m’, ‘400m’, ‘500m’, ‘1g’, ‘2g’, ‘5g’, ‘10g’) for interconnect attachments, not explicitly mentioned in release notes.
  • Added a new multitype.py module, introducing MultitypeConceptSpec and TypedConceptResult to support concepts that can represent multiple resource types, with type resolution based on actively specified attributes.
  • The DEFAULT_LIST_FORMAT for Compute Routes now includes nextHopNetwork, enhancing the displayed information for routes.
  • Added a new IdentityProjector class, a no-op resource projector that preserves the original object, likely for internal use cases.
  • Added regionSslCertificates service to the Compute Alpha client, enabling management of regional SSL certificates.
  • Added regionTargetHttpsProxies service to the Compute Alpha client, enabling management of regional Target HTTPS Proxies.
  • New Compute Alpha API methods for regional SSL certificate management have been added.
  • New Compute Alpha API methods for regional Target HTTPS Proxy management have been added.
  • The GetNatMappingInfo method was added to the Compute Alpha RoutersService, providing new functionality to retrieve NAT mapping information for VM endpoints.
  • The AggregatedList method was added to the Compute Alpha SslCertificatesService, allowing for a combined listing of regional and global SSL certificates.
  • The AggregatedList method was added to the Compute Alpha TargetHttpsProxiesService, providing a way to list all regional and global Target HTTPS Proxies.
  • The full API definition for the new Cloud Filestore service (v1alpha1) has been added to the SDK, allowing interaction with file server instances, volumes, and networks. This is a new service integration not explicitly mentioned in the provided release notes.
  • A new client library for the Cloud TPU v1 API was introduced, enabling interaction with Cloud TPU resources through methods for managing accelerator types, nodes (create, delete, reimage, reset, start, stop), operations, locations, and TensorFlow versions.
  • Introduction of the Cloud TPU v1 API, providing full lifecycle management for TPU nodes.
  • Addition of ‘schedulingConfig’ with a ‘preemptible’ option to the TPU v1alpha1 API for node configuration.

Stats

  • Files changed: 316
  • Inserted lines: +12,722
  • Deleted lines: -3,603

Generated by Gemini - View full diff

Google, Google Cloud, and gcloud are trademarks of Google LLC. This analysis was automatically generated by an AI agent examining only public release artifacts, without access to internal or non-public information from Google Cloud.