* init copy cmd * extract creating emulator connection logic * extract copy args as struct * add new_for_emulator * add tryFrom confirmed block to versioned block * implement bigtable copy command * use 'force' flag to force upload * use unwrap_or * remove redundant importing * fix nightly lint * explicit transactions missing error * process ending_slot * prevent start slot > end slot * print skip slots in debug level * fix destination bigtable should not be readonly * combine is-emulator and endpoint to emulated source. conflict with crenditial path * wording * log some error messages with error level * nightly lint * add dry-run * extract create bigtable instances logic * use a lighter way to check block * use the latest futures version which is used in the repo * use futures = "0.3" Co-authored-by: Tyera <teulberg@gmail.com> * wording Co-authored-by: Tyera <teulberg@gmail.com> * wording Co-authored-by: Tyera <teulberg@gmail.com> Co-authored-by: Tyera <teulberg@gmail.com> |
||
---|---|---|
.. | ||
build-proto | ||
proto | ||
src | ||
Cargo.toml | ||
README.md | ||
init-bigtable.sh |
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:
- Run
gcloud beta emulators bigtable start
in the background - Run
$(gcloud beta emulators bigtable env-init)
to establish theBIGTABLE_EMULATOR_HOST
environment variable - Run
./init-bigtable.sh
to configure the emulator - 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).