Prod Release 13/06/24 #802
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
morgsmccauley
commented
Jun 13, 2024
morgsmccauley
commented
- feat: Expose gRPC service to handle provisioning (feat: Expose gRPC service to handle provisioning #758)
- fixed context db type generation, added overlay(tooltip) component, minor UI changes, Updated Packages and Imports (fixed context db type generation, added overlay(tooltip) component, minor UI changes, Updated Packages and Imports #781)
- Removed Yarn (in favor of NPM ), Updated Docker, Reran/updated packages. (feat: Removed Yarn (in favor of NPM ), Updated Docker, Reran/updated packages. #786)
This PR adds the `DataLayerService`, which allows for provisioning the "Data Layer" of a QueryAPI Indexer. Data Layer in this case refers to the Postgres Database and Hasura GraphQL endpoint. I wanted to move away from the more general "provisioning" term as it is a bit overloaded, and may get conflated with other provisioning steps related to Executors (which may become more involved with Firecracker). This PR doesn't replace the existing provisioning flow - yet, I'll do that in a follow up PR. As provisioning can take some time, rather than keeping the request/connection open while we wait, the `Provision` command triggers the process, and returns immediately. The `CheckProvsioningStatus` command will then be used to poll its completion. On top the new service, the following changes have been made: - the gRPC `server/` directory has been slightly restructured to accommodate additional services, i.e. `DataLayerService`, as a result you'll see lots of `runner` files being moved around - `Provisioner` now takes `ProvisioningConfig`, which is a subset of `IndexerConfig`. On the gRPC side we don't have a full `IndexerConfig`, nor do we need it, so I created the subset to make it possible to provision with only the data we need. `IndexerConfig extends ProvisioningConfig` so it's not a breaking change to the existing use-cases. - I've removed all the unused code in `Provisioner`
…inor UI changes, Updated Packages and Imports (#781) Just some final touch ups. Spoke with Pavel and he requested a few changes here and there. In the push there are the following changes. 1. (HTML/JSX CHANGE): Changed SignUp to (Read The Docs) 2. (HTML/JSX CHANGE): Swapped Component position of indexer height and indexer status in logs 3. (HTML/JSX CHANGE): Renamed App.js to Indexer.js 4. (NEW COMPONENT): Added overlay to buttons 5. (LOGIC REFACTOR/FIX): Fixed context db type generation. Refactored Logic. 6. (CHORE): Updated packages 7. (CHORE): Removed Dead Code and Refactored relative Imports using base '@' 8. (NEW COMPONENT): Added NEAR latest block height
…es. (#786) We previously managed our packages with two different package managers, which often led to confusion and inconsistencies within the repository. Some parts of the codebase used Yarn, while others, like Docker configurations, relied on npm. This setup resulted in numerous dependency mismatches/conflucts, duplicate caching and storage, and larger build times. To align with the majority of our repository, which already uses npm (e.g., our runner scripts), I remove Yarn entirely and standardize on npm. I eliminated all references to Yarn, including removing the yarn.lock file/cache. Additionally, we updated our Dockerfile from using Node.js version 16 to version 18 to meet the requirements of our applications and removed the reference to yarn in our dockerfile. Which is odd because our local dockerfile used yarn while our dockerfile on gcp references npm?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.