Skip to content

feat(memorystore): enable gRPC transport#16927

Merged
noahdietz merged 2 commits intogoogleapis:mainfrom
noahdietz:chore-update-librarian-2026-05-04
May 4, 2026
Merged

feat(memorystore): enable gRPC transport#16927
noahdietz merged 2 commits intogoogleapis:mainfrom
noahdietz:chore-update-librarian-2026-05-04

Conversation

@noahdietz
Copy link
Copy Markdown
Contributor

Updates librarian version to v0.12.0 and regenerates all clients.

This tag picked up a change to the memorystore configuration to enable grpc as a client transport, the changes for which are included in this update.

These were the only changes produced by generate --all.

@noahdietz noahdietz requested review from a team as code owners May 4, 2026 17:48
@snippet-bot
Copy link
Copy Markdown

snippet-bot Bot commented May 4, 2026

Here is the summary of changes.

You are about to add 22 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

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 introduces gRPC and gRPC AsyncIO transport support for the Memorystore client, including the necessary infrastructure, pagers, and generated samples. The reviewer identified a potential security risk regarding the hardcoded gRPC message length limits, which are set to -1 (unlimited) in the new transport implementations, potentially exposing the service to denial-of-service attacks via memory exhaustion.

Comment on lines +264 to +267
options=[
("grpc.max_send_message_length", -1),
("grpc.max_receive_message_length", -1),
],
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.

security-medium medium

Hardcoding gRPC message length limits to -1 (unlimited) can pose a security risk by allowing excessively large messages to consume memory, potentially leading to OOM errors. Consider setting a reasonable upper bound based on expected payload sizes.

Comment on lines +209 to +212
scopes (Optional[Sequence[str]]): A optional list of scopes needed for this
service. These are only used when credentials are not specified and
are passed to :func:`google.auth.default`.
channel (Optional[Union[aio.Channel, Callable[..., aio.Channel]]]):
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.

security-medium medium

Hardcoding gRPC message length limits to -1 (unlimited) can pose a security risk by allowing excessively large messages to consume memory, potentially leading to OOM errors. Consider setting a reasonable upper bound based on expected payload sizes.

Comment on lines +264 to +267
options=[
("grpc.max_send_message_length", -1),
("grpc.max_receive_message_length", -1),
],
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.

security-medium medium

Hardcoding gRPC message length limits to -1 (unlimited) can pose a security risk by allowing excessively large messages to consume memory, potentially leading to OOM errors. Consider setting a reasonable upper bound based on expected payload sizes.

Comment on lines +209 to +212
scopes (Optional[Sequence[str]]): A optional list of scopes needed for this
service. These are only used when credentials are not specified and
are passed to :func:`google.auth.default`.
channel (Optional[Union[aio.Channel, Callable[..., aio.Channel]]]):
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.

security-medium medium

Hardcoding gRPC message length limits to -1 (unlimited) can pose a security risk by allowing excessively large messages to consume memory, potentially leading to OOM errors. Consider setting a reasonable upper bound based on expected payload sizes.

@noahdietz noahdietz merged commit 71b73e5 into googleapis:main May 4, 2026
30 checks passed
@noahdietz noahdietz deleted the chore-update-librarian-2026-05-04 branch May 4, 2026 18:24
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