-
Notifications
You must be signed in to change notification settings - Fork 84
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
cluster: unique validator_keys dir #2958
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2958 +/- ##
==========================================
+ Coverage 54.09% 54.12% +0.03%
==========================================
Files 194 194
Lines 27402 27412 +10
==========================================
+ Hits 14822 14838 +16
+ Misses 10826 10821 -5
+ Partials 1754 1753 -1 ☔ View full report in Codecov by Sentry. |
I'm not sure this is better. People would struggle to figure out why their validator keys aren't matching with the expected ones because their cluster has imported the default |
Thank you @OisinKyne, changed as you suggested. Good point. |
f14abff
to
6ea4107
Compare
Quality Gate passedIssues Measures |
In according with the issue description #2881, this is UX improvement - if the target validator_keys folder exists, the implementation checks if the folder is empty. If the existing directory is not empty, or in case of any IO error, the process fails.
category: feature
ticket: #2881