Skip to content

Conversation

@bhshkh
Copy link
Contributor

@bhshkh bhshkh commented Jan 22, 2026

PiperOrigin-RevId: 799477610

@bhshkh bhshkh requested review from a team as code owners January 22, 2026 14:47
@bhshkh bhshkh enabled auto-merge (squash) January 22, 2026 14:47
@snippet-bot
Copy link

snippet-bot bot commented Jan 22, 2026

Here is the summary of changes.

You are about to add 57 region tags.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @bhshkh, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates the new Cloud Security Compliance API into the existing Go client libraries. It provides developers with a dedicated and fully generated client to programmatically manage and monitor cloud security compliance resources, streamlining the adoption and interaction with this new Google Cloud service.

Highlights

  • New Client Library Introduction: This pull request introduces a new Go client library for the Cloud Security Compliance API, enabling Go developers to interact with its services.
  • Configuration Update: The .librarian/state.yaml file has been updated to include the new cloudsecuritycompliance library, specifying its ID, version, API paths, source roots, and regex patterns for file management.
  • Generated Client Code: A comprehensive set of generated client code has been added under cloudsecuritycompliance/apiv1/, including client implementations for Audit, CM Enrollment, Config, and Monitoring services, along with their respective protobuf definitions, gRPC interfaces, and example usage files for various Go versions.
  • Module and Metadata Files: New CHANGES.md, README.md, .repo-metadata.json, go.mod, go.sum, and version.go files have been added to properly define and manage the new cloudsecuritycompliance Go module.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces new client libraries for the cloudsecuritycompliance service. The changes include adding the service definition to .librarian/state.yaml, creating a new CHANGES.md and README.md for the service, and generating the Go client code, protobuf definitions, gRPC and REST client implementations, example usage, and Go module files. The generated code adheres to standard patterns for Google Cloud Go client libraries. No critical issues were found in the changes.

@bhshkh bhshkh merged commit fedc428 into googleapis:main Jan 22, 2026
12 checks passed
@bhshkh bhshkh deleted the librarian-onboard-cloudsecuritycompliance branch January 22, 2026 17:46
bhshkh added a commit that referenced this pull request Jan 26, 2026
The new client added in
#13660 did not get
added to snippets go.mod.
This led to multiple build failures e.g.
#13714
gagangupt16 pushed a commit to gagangupt16/google-cloud-go that referenced this pull request Jan 27, 2026
The new client added in
googleapis#13660 did not get
added to snippets go.mod.
This led to multiple build failures e.g.
googleapis#13714
krishnamd-jkp pushed a commit that referenced this pull request Jan 28, 2026
krishnamd-jkp pushed a commit that referenced this pull request Jan 28, 2026
The new client added in
#13660 did not get
added to snippets go.mod.
This led to multiple build failures e.g.
#13714
parthea pushed a commit that referenced this pull request Jan 29, 2026
PR created by the Librarian CLI to initialize a release. Merging this PR
will auto trigger a release.

Librarian Version: v0.0.0-20251218164811-cd2252e38d0a
Language Image:
us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/librarian-go@sha256:01189c9771ac4150742aed38eb52e19a008018889066002742034b7f82db070f
<details><summary>apiregistry: 0.2.0</summary>

##
[0.2.0](apiregistry/v0.1.0...apiregistry/v0.2.0)
(2026-01-29)

### Features

* add new clients (#13723) (PiperOrigin-RevId: 860067834)
([c639b28](c639b283))

</details>


<details><summary>cloudquotas: 1.5.0</summary>

##
[1.5.0](cloudquotas/v1.4.0...cloudquotas/v1.5.0)
(2026-01-29)

### Documentation

* another bulk typo correction (#13527)
([90a4f21](90a4f21f))

* fix typo in README.md entries (#13526)
([ac32b85](ac32b851))

* Correct typo in comment for field `quota_id` (PiperOrigin-RevId:
859139909)
([d8ea738](d8ea738a))

</details>


<details><summary>cloudsecuritycompliance: 0.1.0</summary>

##
[0.1.0](cloudsecuritycompliance/v0.0.0...cloudsecuritycompliance/v0.1.0)
(2026-01-29)

### Features

* add new clients (#13660) (PiperOrigin-RevId: 799477610)
([fedc428](fedc428c))

</details>


<details><summary>container: 1.46.0</summary>

##
[1.46.0](container/v1.45.0...container/v1.46.0)
(2026-01-29)

### Features

* Add NodeDrainConfig to NodePool to configure node draining behavior
(PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* Add RegistryHostConfig to ContainerdConfig for containerd registry
host configuration (PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* Add ManagedOpenTelemetryConfig to Cluster to manage the OpenTelemetry
pipeline (PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* Add AutopilotGeneralProfile to ClusterAutoscaling to configure
Autopilot profiles (PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* Add SHORT_LIVED as a NodePoolUpdateStrategy (PiperOrigin-RevId:
859731311)
([d8ea738](d8ea738a))

* Add SliceControllerConfig to AddonsConfig to manage the Slice
Controller addon (PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* Add SwapConfig to enable and configure swap memory for node pools
(PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* Add DisruptionEvent to provide details on node disruption events
(PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* Add DRAINING status to AdditionalIPRangesConfig for subnet draining
(PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* Add consolidation_delay to configure Cluster Autoscaler node
consolidation delay (PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* Add GPUDirectConfig to configure GPU Direct for node pools
(PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* Allow specifying subnetwork in NodeNetworkConfig during node pool
creation (PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

### Documentation

* A comment for field `cluster_ipv4_cidr_block` in message
`.google.container.v1.IPAllocationPolicy` is changed (PiperOrigin-RevId:
859731311)
([d8ea738](d8ea738a))

* A comment for field `subnetwork` in message
`.google.container.v1.NodeNetworkConfig` is changed (PiperOrigin-RevId:
859731311)
([d8ea738](d8ea738a))

* A comment for field `tpu_ipv4_cidr_block` in message
`.google.container.v1.IPAllocationPolicy` is changed (PiperOrigin-RevId:
859731311)
([d8ea738](d8ea738a))

* A comment for field `recurrence` in message
`.google.container.v1.RecurringTimeWindow` is changed
(PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* A comment for field `services_ipv4_cidr_block` in message
`.google.container.v1.IPAllocationPolicy` is changed (PiperOrigin-RevId:
859731311)
([d8ea738](d8ea738a))

* A comment for field `services_ipv4_cidr` in message
`.google.container.v1.Cluster` is changed (PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* A comment for field `tpu_ipv4_cidr_block` in message
`.google.container.v1.Cluster` is changed (PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* A comment for field `sysctls` in message
`.google.container.v1.LinuxNodeConfig` is changed (PiperOrigin-RevId:
859731311)
([d8ea738](d8ea738a))

* A comment for field `cluster_ipv4_cidr` in message
`.google.container.v1.Cluster` is changed (PiperOrigin-RevId: 859731311)
([d8ea738](d8ea738a))

* A comment for field `node_ipv4_cidr_block` in message
`.google.container.v1.IPAllocationPolicy` is changed (PiperOrigin-RevId:
859731311)
([d8ea738](d8ea738a))

* A comment for field `gcp_secret_manager_certificate_config` in message
`.google.container.v1.ContainerdConfig` is changed (PiperOrigin-RevId:
859731311)
([d8ea738](d8ea738a))

</details>


<details><summary>documentai: 1.40.0</summary>

##
[1.40.0](documentai/v1.39.0...documentai/v1.40.0)
(2026-01-29)

### Documentation

* Fixed language issues in multiple message field descriptions
(PiperOrigin-RevId: 859310712)
([d8ea738](d8ea738a))

* Regenerated REST and RPC Document AI documentation to include missing
changes from September 2024 to November 2025 (PiperOrigin-RevId:
859310712)
([d8ea738](d8ea738a))

</details>


<details><summary>networkmanagement: 1.22.0</summary>

##
[1.22.0](networkmanagement/v1.21.0...networkmanagement/v1.22.0)
(2026-01-29)

### Features

* add fields and messages for GKE Pods and IP masquerading
(PiperOrigin-RevId: 859595508)
([d8ea738](d8ea738a))

</details>


<details><summary>retail: 1.26.0</summary>

##
[1.26.0](retail/v1.25.1...retail/v1.26.0)
(2026-01-29)

### Features

* add a user_attributes field in SearchRequest that can be used for
personalization (PiperOrigin-RevId: 861314205)
([d8ea738](d8ea738a))

* add a model_scores field in SearchResponse.results to expose model
quality signals (PiperOrigin-RevId: 861314205)
([d8ea738](d8ea738a))

</details>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants