[HEALTH] Extract health endpoint definition into blockscout-health crate #894
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
rimrakhimov
changed the base branch from
main
to
rimrakhimov/visualizer/extract-health
sevenzing
approved these changes
Jul 3, 2024
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.
Extract health proto and actix-prost definition builds into a separate lib. That allows not to add health endpoints into
api_config_http.yamland not to specfy that#[serde(default)]field attribute for.grpc.health.v1.HealthCheckRequest.servicein each service.As a downside, the health endpoint would be missing from the resultant swagger.
Implemented as a separate crate, because we need a
build.rsscript to explicitly build only those definitions