solana/storage-bigtable
dependabot[bot] 0d9d7f044c
chore: bump either from 1.6.1 to 1.7.0 (#26787)
* chore: bump either from 1.6.1 to 1.7.0

Bumps [either](https://github.com/bluss/either) from 1.6.1 to 1.7.0.
- [Release notes](https://github.com/bluss/either/releases)
- [Commits](https://github.com/bluss/either/compare/1.6.1...1.7.0)

---
updated-dependencies:
- dependency-name: either
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* [auto-commit] Update all Cargo lock files

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: dependabot-buildkite <dependabot-buildkite@noreply.solana.com>
2022-07-26 10:56:31 -06:00
..
build-proto chore: bump either from 1.6.1 to 1.7.0 (#26787) 2022-07-26 10:56:31 -06:00
proto Fix derive_partial_eq_without_eq clippy lint 2022-05-22 22:22:21 -07:00
src bigtable: set_nodelay for http connector (#26398) 2022-07-25 15:16:55 -06:00
Cargo.toml chore: bump http from 0.2.6 to 0.2.8 (#26777) 2022-07-25 15:19:52 -06:00
README.md bigtable: allow forward proxy in gRPC connection (#25918) 2022-06-23 10:51:31 -06:00
init-bigtable.sh Add configuration info 2020-08-05 14:27:12 -07:00

README.md

BigTable Setup

Development Environment

The Cloud BigTable emulator can be used during development/test. See https://cloud.google.com/bigtable/docs/emulator for general setup information.

Process:

  1. Run gcloud beta emulators bigtable start in the background
  2. Run $(gcloud beta emulators bigtable env-init) to establish the BIGTABLE_EMULATOR_HOST environment variable
  3. Run ./init-bigtable.sh to configure the emulator
  4. Develop/test

Production Environment

Export a standard GOOGLE_APPLICATION_CREDENTIALS environment variable to your service account credentials. The project should contain a BigTable instance called solana-ledger that has been initialized by running the ./init-bigtable.sh script.

Depending on what operation mode is required, either the https://www.googleapis.com/auth/bigtable.data or https://www.googleapis.com/auth/bigtable.data.readonly OAuth scope will be requested using the provided credentials.

Forward proxy

Export BIGTABLE_PROXY environment variable for the forward proxy as you would for HTTP_PROXY. This will establish a tunnel through the forward proxy for gRPC traffic (the tunneled traffic will still use TLS as normal).