| commit | 633bd13d1915a17bddd99e6891c36546d72555ae | [log] [tgz] |
|---|---|---|
| author | Wendy Wang <wendy.wang10@sap.com> | Thu Aug 03 18:17:25 2023 +0200 |
| committer | Wendy Wen Wang <wendy.wang10@sap.com> | Mon Sep 04 11:57:14 2023 +0000 |
| tree | d7dbb4cb77c2e5c909c5388bab123a3e5940a322 | |
| parent | c007a8d390628c99ed7bf6102809a5333419b969 [diff] |
Remove Unnecessary Code/Add Code Reuse getSpannerInstance() is unused and unnecessary. Additionally, the existence check can re-use the get() method. Change-Id: I0a2b7b0fdc7173b22ce611670d8196a26c059ec4
This plugin provides an implementation of the Gerrit global refdb backed by Cloud Spanner.
Requirements for using this plugin are:
A global refdb implementation is a requirement for a Gerrit multi-master scenario in a multi-site setup to ensure refs are updated consistently across multiple Gerrit primary sites.
Refer to the Gerrit multi-site plugin for more details on the high level architecture.
The in-memory Cloud Spanner emulator can be used during development. There are several limitations of the emulator that differ from the production service.
An easy way to run the emulator is to use gcloud CLI and Docker. Following the install instructions here will provide a local instance that the plugin can access. The gcloud CLI commands will be sent to the emulator instead of the production service. A test spanner instance and database will need to be created.
gcloud spanner instances create test-instance --config=emulator-config --description="Test Instance" --nodes=1 gcloud spanner databases create global-refdb --instance=test-instance
There are several limitations of the emulator which differ from the production service.
In order to easily set up and begin testing the spanner-refdb plugin, the multi-site plugin's local environment setup can be used.
This simulates a multi-site setup using two local gerrit instances. Build the release.war to include spanner-refdb and follow the linked example setup.
Configuration details can be found in the spanner-refdb config documentation.
When not used with the emulator, the plugin requires the path to credentials in the config to authenticate with google. To create the key see the official documentation.