#bigtable #emulator #variables #cloud #env-var #google #environment

waffles-solana-storage-bigtable

Waffle Labs maintained Solana Storage BigTable

7 releases

1.16.0-alpha.10 Mar 24, 2023
1.16.0-alpha.9 Mar 23, 2023
1.16.0-alpha.5 Feb 27, 2023

#4 in #bigtable

Download history 27/week @ 2024-06-17 43/week @ 2024-06-24 5/week @ 2024-07-01 9/week @ 2024-07-08 28/week @ 2024-07-15 15/week @ 2024-07-22 92/week @ 2024-07-29 19/week @ 2024-08-05 27/week @ 2024-08-12 15/week @ 2024-08-19 6/week @ 2024-08-26 13/week @ 2024-09-02 18/week @ 2024-09-09 17/week @ 2024-09-16 43/week @ 2024-09-23 27/week @ 2024-09-30

105 downloads per month
Used in 12 crates (4 directly)

Apache-2.0

1.5MB
27K SLoC

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).

Dependencies

~47–71MB
~1.5M SLoC