Support auto-configuration of the Datastore emulator #1642
Comments
|
I created the issue on google github here and I will submit the PR accepting a custom port. We should also consider to make this same approach to all google's emulators. |
|
@meltsufin google cloud lauched the release with my modification accepting port on the datastore emulator: |
|
@lucasoares Would you be interested in a contributing a PR for it? |
|
@meltsufin I can help with that but I'm not a spring contributor.. To do that I will need to change datastore client's version, but spring use the google client BOM in Please look at the PR and let me know about my concerns. If I continue with the contribution I will try to enter in some community chat to ask ppl questions like that. Thank you. |
- Support for `spring.cloud.gcp.datastore.emulator.enabled` property - `spring.cloud.gcp.datastore.emulator-host` deprecated in favor of `spring.cloud.gcp.datastore.host` - The autoconfiguration itself manage the lifecycle to start and stop the emulator Fixes #1642.
Currently, we support the Datastore emulator by allowing the client to configure host and port via the
spring.cloud.gcp.datastore.emulator-hostproperty. However, it remains the user's responsibility to start and stop the emulator.The proposal is to add the
spring.cloud.gcp.datastore.emulator=trueproperty to automatically configure the emulator, start, and stop it.LocalDatastoreHelperfromgoogle-cloud-javacan be used to accomplish it.See discussion here.
The text was updated successfully, but these errors were encountered: