Skip to content

Conversation

@cloud-java-bot
Copy link
Collaborator

@cloud-java-bot cloud-java-bot commented Dec 16, 2024

Generated by @JoeWang1127 via generate_new_client_hermetic_build.yaml

Command used:

python generation/new_client_hermetic_build/add-new-client-config.py add-new-client --api-shortname "memorystore" --name-pretty "Memorystore API" --api-description "Memorystore for Valkey is a fully managed Valkey Cluster service for Google Cloud." --proto-path "google/cloud/memorystore/v1beta" --product-docs "https://cloud.google.com/memorystore/docs/valkey" --rest-docs "https://cloud.google.com/memorystore/docs/valkey/reference/rest" 

b/376713169
b/376713261

@cloud-java-bot cloud-java-bot requested a review from a team as a code owner December 16, 2024 14:44
@cloud-java-bot cloud-java-bot added the owlbot:run Add this label to trigger the Owlbot post processor. label Dec 16, 2024
@snippet-bot
Copy link

snippet-bot bot commented Dec 16, 2024

Here is the summary of changes.

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

Comment on lines +1439 to +1443
product_documentation: https://cloud.google.com/memorystore/docs/valkey
api_description: Memorystore for Valkey is a fully managed Valkey Cluster service
for Google Cloud.
client_documentation:
https://cloud.google.com/java/docs/reference/google-cloud-memorystore/latest/overview
Copy link
Member

Choose a reason for hiding this comment

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

Product documentation is specific to valkey, but client documentation is generic.

Are we going to have collision issues with any of these other Memorystore variants? https://cloud.google.com/memorystore/docs/
(Redis, Redis Cluster, Memcached)

Copy link
Contributor

@JoeWang1127 JoeWang1127 Dec 16, 2024

Choose a reason for hiding this comment

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

The client doc is unique if the artifact is unique, google-cloud-memorystore, in this case.

If you think memorystore is too generic, how about we change the artifact id to google-cloud-valkey? Redis, Redis Cluster, Memcached are all followed this pattern.

Copy link
Member

Choose a reason for hiding this comment

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

Yes - following the existing pattern would be great -- thank you.

@JoeWang1127 JoeWang1127 merged commit a859630 into main Dec 16, 2024
31 checks passed
@JoeWang1127 JoeWang1127 deleted the new-library/memorystore-0Jhea branch December 16, 2024 16:24
lqiu96 pushed a commit that referenced this pull request Jul 7, 2025
* feat: [memorystore] new module for memorystore

* chore: generate libraries at Mon Dec 16 14:46:47 UTC 2024

* add v1

* chore: generate libraries at Mon Dec 16 14:51:36 UTC 2024

* change to valkey

* chore: generate libraries at Mon Dec 16 15:59:04 UTC 2024

* chore: generate libraries at Mon Dec 16 16:02:22 UTC 2024

* remove generated module

---------

Co-authored-by: Joe Wang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

owlbot:run Add this label to trigger the Owlbot post processor.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants