-
Notifications
You must be signed in to change notification settings - Fork 329
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
Add support for specifying Firestore/Datastore DBs #2145
Labels
Comments
Memo: This "contain" means "limit". This is a request to limit a (micro)service to use only a certain "database" (Pre-GA Offerings) https://cloud.google.com/firestore/docs/manage-databases#create_a_database. |
I'm looking for the same mechanism too :) |
MarcinLachowicz
pushed a commit
to MarcinLachowicz/spring-cloud-gcp
that referenced
this issue
Sep 4, 2023
MarcinLachowicz
pushed a commit
to MarcinLachowicz/spring-cloud-gcp
that referenced
this issue
Sep 4, 2023
MarcinLachowicz
added a commit
to MarcinLachowicz/spring-cloud-gcp
that referenced
this issue
Sep 4, 2023
MarcinLachowicz
added a commit
to MarcinLachowicz/spring-cloud-gcp
that referenced
this issue
Sep 4, 2023
Created a PR for Datastore: #2150 |
meltsufin
added a commit
that referenced
this issue
Sep 13, 2023
meltsufin
added a commit
that referenced
this issue
Sep 19, 2023
Also adds routing headers for all Firestore requests. Fixes #2145.
meltsufin
added a commit
that referenced
this issue
Sep 19, 2023
Also adds routing headers for all Firestore requests. Fixes #2145.
meltsufin
added a commit
that referenced
this issue
Sep 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
It is currently quite difficult to contain a Firestore/Datastore database to a single microservice. Currently the only solution is to use the (default) database and ensure microservices do not use the same collection names.
Describe the solution you'd like
GCP has recently added support for multiple databases, meaning it's now possible to assign one per microservice. This could possibly be implemented by creating an optional system property such as
spring.cloud.gcp.firestore.database = "xyz"
Describe alternatives you've considered
This could also possibly be implemented by adding the field to a Document annotation such as
@Document(collectionName="users", databaseName="xyz")
Thanks!
The text was updated successfully, but these errors were encountered: