-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: [memorystore] new module for memorystore #11356
Conversation
…/google-cloud-java into new-library/memorystore-0Jhea
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 |
There was a problem hiding this comment.
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)
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
…/google-cloud-java into new-library/memorystore-0Jhea
…/google-cloud-java into new-library/memorystore-0Jhea
Generated by @JoeWang1127 via generate_new_client_hermetic_build.yaml
Command used:
b/376713169
b/376713261