Skip to content

chore: librarian generate pull request: 20260311T104913Z#16073

Merged
parthea merged 1 commit intomainfrom
librarian-20260311T104913Z
Mar 11, 2026
Merged

chore: librarian generate pull request: 20260311T104913Z#16073
parthea merged 1 commit intomainfrom
librarian-20260311T104913Z

Conversation

@parthea
Copy link
Copy Markdown
Contributor

@parthea parthea commented Mar 11, 2026

PR created by the Librarian CLI to generate Cloud Client Libraries code from protos.

BEGIN_COMMIT

BEGIN_NESTED_COMMIT
feat: Add BigtableConfig type

PiperOrigin-RevId: 878685355
Library-IDs: google-cloud-pubsub
Source-link: googleapis/googleapis@23ec7b6e
END_NESTED_COMMIT

END_COMMIT

This pull request is generated with proto changes between
googleapis/googleapis@ce8678a9
(exclusive) and
googleapis/googleapis@23ec7b6e
(inclusive).

Librarian Version: v1.0.2-0.20260309131826-42ac5c451239
Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:160860d189ff1c2f7515638478823712fa5b243e27ccc33a2728669fa1e2ed0c

@parthea parthea requested review from a team as code owners March 11, 2026 10:50
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 automates the generation of Cloud Client Libraries code for Google Cloud Pub/Sub. The primary change is the addition of a BigtableConfig type, which enables Pub/Sub subscriptions to be configured for message delivery to Bigtable, thereby enhancing integration capabilities with Bigtable.

Highlights

  • New Feature: BigtableConfig: Introduced the BigtableConfig type to support configuring Pub/Sub subscriptions for message delivery to Google Cloud Bigtable.
Changelog
  • .librarian/state.yaml
    • Updated the last_generated_commit for the google-cloud-pubsub library to reflect the latest code generation.
  • packages/google-cloud-pubsub/google/pubsub/init.py
    • Added BigtableConfig to the list of imported and exported types.
  • packages/google-cloud-pubsub/google/pubsub_v1/init.py
    • Added BigtableConfig to the list of imported and exported types.
  • packages/google-cloud-pubsub/google/pubsub_v1/types/init.py
    • Added BigtableConfig to the list of imported and exported types.
  • packages/google-cloud-pubsub/google/pubsub_v1/types/pubsub.py
    • Defined the BigtableConfig message, including its fields (table, app_profile_id, service_account_email, write_metadata, state) and the nested State enum with various possible states for a Bigtable subscription.
    • Integrated bigtable_config as an optional field into the Subscription message, allowing users to specify Bigtable delivery configurations.
Activity
  • The pull request was automatically generated by the Librarian CLI.
  • No human comments or reviews have been recorded yet.
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
Copy Markdown
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, generated by the Librarian CLI, introduces the BigtableConfig type for Pub/Sub subscriptions. The changes are mostly correct, and the minor issues previously identified regarding field ordering and a typo in the docstring remain valid and would improve code quality and consistency.


- row key: subscription name and message ID delimited by #.
- columns: message bytes written to a single column family
"data" with an empty-string column qualifier.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

There seems to be a minor typo here with extra spaces. It should be 'an empty-string' instead of 'an empty-string'.

Suggested change
"data" with an empty-string column qualifier.
"data" with an empty-string column qualifier.

Comment on lines +2781 to +2801
table: str = proto.Field(
proto.STRING,
number=1,
)
app_profile_id: str = proto.Field(
proto.STRING,
number=2,
)
service_account_email: str = proto.Field(
proto.STRING,
number=3,
)
write_metadata: bool = proto.Field(
proto.BOOL,
number=5,
)
state: State = proto.Field(
proto.ENUM,
number=4,
enum=State,
)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

For better readability and consistency with other message definitions in this file, it's recommended to order the fields by their number attribute. The state field (number=4) should come before the write_metadata field (number=5).

    table: str = proto.Field(
        proto.STRING,
        number=1,
    )
    app_profile_id: str = proto.Field(
        proto.STRING,
        number=2,
    )
    service_account_email: str = proto.Field(
        proto.STRING,
        number=3,
    )
    state: State = proto.Field(
        proto.ENUM,
        number=4,
        enum=State,
    )
    write_metadata: bool = proto.Field(
        proto.BOOL,
        number=5,
    )

Copy link
Copy Markdown
Contributor

@chalmerlowe chalmerlowe left a comment

Choose a reason for hiding this comment

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

LGTM

@chalmerlowe chalmerlowe added the automerge Merge the pull request once unit tests and other checks pass. label Mar 11, 2026
@parthea parthea merged commit ec1a676 into main Mar 11, 2026
54 of 60 checks passed
@parthea parthea deleted the librarian-20260311T104913Z branch March 11, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Merge the pull request once unit tests and other checks pass.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants