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
🎯 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-pathflag for charon test peers command--cluster-lock-pathflag for charon test peers command--enrs, but one of the 3--enrs,--cluster-definition-pathor--cluster-lock-path🧪 Tests