chore: temporarily block generation to facilitate gradual rollout

[parthea]

Temporarily disable generation for all packages except

google-cloud-bigquery-storage
google-cloud-discoveryengine
google-cloud-secret-manager
google-cloud-speech

We would like to generate and release these libraries as part of a gradual rollout. This will be reverted once the libraries are generated/released

[gemini-code-assist]

Summary of Changes

Hello @parthea, I'm Gemini Code Assist¹! 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 implements a temporary measure to control the automatic generation of client libraries. By blocking generation for the majority of packages, it enables a focused, gradual rollout of a select few, ensuring a more controlled release process. The change is designed to be short-lived, with a clear plan for reversion once the immediate rollout objectives are met.

Highlights

• Temporary Generation Block: Most libraries are temporarily blocked from automatic generation to facilitate a gradual rollout process for specific Google Cloud libraries.
• Enabled Libraries for Rollout: Generation remains active only for google-cloud-bigquery-storage, google-cloud-discoveryengine, google-cloud-secret-manager, and google-cloud-speech as part of this phased release.
• Reversion Plan: This configuration change is temporary and will be reverted once the selected libraries have been successfully generated and released.

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

[gemini-code-assist]

Code Review

This pull request temporarily blocks code generation for a large number of libraries by adding them to a blocklist in .librarian/config.yaml. This is intended to allow for a gradual rollout of a few specific libraries. While the change correctly implements the described goal, the resulting configuration file is very long and hard to maintain. My review includes a suggestion to investigate a more concise configuration approach, such as an allow-list, if the tooling supports it, to improve maintainability.

[gemini-code-assist]

This large deny-list is difficult to maintain and review. For better maintainability, especially for a temporary change that will be reverted, an allow-list pattern is preferable. If the underlying tooling supports it, please consider refactoring this to block generation by default and explicitly enable it for the few required libraries. This would make the configuration much more concise and manageable.

An allow-list approach might look something like this:

# Hypothetical example
generate_all_blocked: true
libraries:
- id: "google-cloud-bigquery-storage"
  generate_blocked: false
- id: "google-cloud-discoveryengine"
  generate_blocked: false
- id: "google-cloud-secret-manager"
  generate_blocked: false
- id: "google-cloud-speech"
  generate_blocked: false