Skip to content
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

Support passing of headers to all Engine API calls #11330

Merged
merged 3 commits into from
Aug 29, 2022

Conversation

lyzs90
Copy link
Contributor

@lyzs90 lyzs90 commented Aug 27, 2022

What type of PR is this?

Feature

What does this PR do? Why is it needed?

Adds a Beacon Node CLI flag --execution-headers to allow setting of HTTP headers on all execution engine API calls. Implementation is by and large similar to that of --grpc-headers on the validator.

Which issues(s) does this PR fix?

Fixes #11149

Other notes for review

@lyzs90 lyzs90 requested a review from a team as a code owner August 27, 2022 16:05
@lyzs90 lyzs90 requested review from kasey, saolyn and nisdas August 27, 2022 16:05
ExecutionEngineHeaders = &cli.StringFlag{
Name: "execution-headers",
Usage: "A comma separated list of key value pairs to pass as HTTP headers for all execution " +
"client calls. Example: --execution-headers=key=value",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can the example have 2 headers please?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated!

@prylabs-bulldozer prylabs-bulldozer bot merged commit 97dc86e into prysmaticlabs:develop Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Flag to define headers in engine API requests
3 participants