Merge pull request #1021 from near/main

Prod Release 24/09/24

.gitignore

@@ -6,3 +6,5 @@ redis/
 node_modules/
 .vscode/
 runner/yarn.lock
+**/.DS_Store
+

README.md

@@ -39,27 +39,12 @@ Runner:
 - `AWS_ACCESS_KEY_ID`
 - `AWS_SECRET_ACCESS_KEY`
 
-Coordinator:
-- `LAKE_AWS_ACCESS_KEY`
-- `LAKE_AWS_SECRET_ACCESS_KEY`
-- `QUEUE_AWS_ACCESS_KEY`
-- `QUEUE_AWS_SECRET_ACCESS_KEY`
+Block Streamer:
+- `AWS_ACCESS_KEY_ID`
+- `AWS_SECRET_ACCESS_KEY`
 
 These should be populated with your credentials. In most cases, the same key pair can be used for all 3 sets of credentials. Just ensure the keys have permissions to access S3 for handling [Requestor Pays](https://docs.aws.amazon.com/AmazonS3/latest/userguide/RequesterPaysBuckets.html) in Near Lake. 
 
-### Hasura Configuration
-Hasura contains shared tables for e.g. logging and setting arbitrary state. These tables must be configured prior to running the entire QueryApi application. Configuration is stored in the `hasura/` directory and deployed through the Hasura CLI.
-
-To configure Hasura, first start it with:
-```sh
-docker compose up hasura-graphql --detach
-```
-
-And apply the configuration with:
-```sh
-cd ./hasura && hasura deploy
-```
-
 ### Running QueryApi
 With everything configured correctly, we can now start all components of QueryApi with:
 ```sh

coordinator/Cargo.toml

@@ -12,6 +12,7 @@ tokio = "1.28"
 tonic = "0.10.2"
 tracing = "0.1.40"
 tracing-subscriber = { version = "0.3.18", features = ["env-filter"] }
+tracing-stackdriver = "0.10.0"
 serde = "1.0.195"
 serde_json = "1.0.108"