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

🎨 Remove -c flag and global config file for validatorctl #125

Open
TylerGillson opened this issue Aug 2, 2024 · 1 comment
Open

🎨 Remove -c flag and global config file for validatorctl #125

TylerGillson opened this issue Aug 2, 2024 · 1 comment
Labels
refactoring Refactoring / tech debt

Comments

@TylerGillson
Copy link
Member

Summary

The global config file is pointless and should be removed. It's a hold over from palette-cli.

We should preserve -w though, to allow folks to control the top-level dir under which validator config files are written.

@TylerGillson TylerGillson added the refactoring Refactoring / tech debt label Aug 2, 2024
Copy link

dosubot bot commented Nov 1, 2024

Hi, @TylerGillson. I'm helping the validatorctl team manage their backlog and am marking this issue as stale.

You proposed the removal of the -c flag and the global config file for validatorctl, arguing that the config file is unnecessary and a leftover from palette-cli. You also recommended retaining the -w flag for users to specify the top-level directory for validator config files. However, there hasn't been any additional activity or comments on this issue since you opened it.

Could you please let us know if this issue is still relevant to the latest version of the validatorctl repository? If it is, feel free to comment here to keep the discussion going. Otherwise, you can close the issue yourself, or it will be automatically closed in 7 days. Thank you!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 1, 2024
@TylerGillson TylerGillson removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Refactoring / tech debt
Projects
None yet
Development

No branches or pull requests

1 participant