-
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
Rename web3 provider flag to execution endpoint #11133
Conversation
// ExecutionEngineEndpoint provides an HTTP access endpoint to connect to an execution client on the execution layer | ||
ExecutionEngineEndpoint = &cli.StringFlag{ | ||
Name: "execution-endpoint", | ||
Usage: "An execution client http endpoint. Can contain auth header as well in the format", |
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.
If you add an alias for the old flag name, then this isn't really a breaking change.
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.
Good pt. I added the alias but updated the default port to 8551 since 8545 is no longer relevant post merge. Due to port changes, it's breaking now
cmd/beacon-chain/flags/base.go
Outdated
Name: "execution-endpoint", | ||
Usage: "An execution client http endpoint. Can contain auth header as well in the format", | ||
Value: "http://localhost:8551", | ||
Aliases: []string{"http-web3provider"}, |
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.
I'm tempted to add this alias, so it's not a complete breaker, anyone has an opinion here?
Rename
--http-web3provider
to--execution-endpoint
. Change default default port to 8551