You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when we want to test our connection with peers, we require peers' ENRs to be passed as a flag. However, this can be a bit tedious process, especially for non-technical people. We can obtain the peers' ENRs from either the cluster definition or cluster lock files. We should allow to pass one of those as well.
🛠️ Proposed solution
Add --cluster-definition-path flag for charon test peers command
Add --cluster-lock-path flag for charon test peers command
Make require flag not --enrs, but one of the 3 --enrs, --cluster-definition-path or --cluster-lock-path
Fetch peers from definition / lock file and use them for the charon test peers command
🧪 Tests
Tested by new automated unit tests
The text was updated successfully, but these errors were encountered:
🎯 Problem to be solved
Currently when we want to test our connection with peers, we require peers' ENRs to be passed as a flag. However, this can be a bit tedious process, especially for non-technical people. We can obtain the peers' ENRs from either the cluster definition or cluster lock files. We should allow to pass one of those as well.
🛠️ Proposed solution
--cluster-definition-path
flag for charon test peers command--cluster-lock-path
flag for charon test peers command--enrs
, but one of the 3--enrs
,--cluster-definition-path
or--cluster-lock-path
🧪 Tests
The text was updated successfully, but these errors were encountered: