-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onboard validator's Beacon REST API usage to e2e tests #11704
Onboard validator's Beacon REST API usage to e2e tests #11704
Conversation
…riceVignola/prysm into user/pavignol/add-rest-api-e2e-tests
…vignol/add-rest-api-e2e-tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a misunderstanding on how grpc is used in our evaluators. All these evaluators query the beacon-node
not the validator
. So there is no need to change the format of the connection to validatorHelpers.NodeConnection
. The evaluators will still work as expected because they query the beacon node, and whether the validator is running via grpc or the beacon rest-api makes no difference to this.
…vignol/add-rest-api-e2e-tests
…vignol/add-rest-api-e2e-tests
…vignol/add-rest-api-e2e-tests
What type of PR is this?
Feature
What does this PR do? Why is it needed?
It onboards the validator's Beacon REST API usage to the e2e tests by going through the following steps:
use_beacon_api
buildtime flag to a--enable-beacon-rest-api
flagvalidatorHelpers.NodeConnection
as an argument instead of a*grpc.ClientConn
. There's unfortunately not a clean way to do this without touching a bunch of files, but the change is actually simple andvalidatorHelpers.NodeConnection
is simply a wrapper around*grpc.ClientConn
. The behavior of existing e2e tests will not change.--enable-beacon-rest-api
flag.