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

🌱 Add validator Helm chart location override for dev #202

Open
mattwelke opened this issue Aug 27, 2024 · 1 comment
Open

🌱 Add validator Helm chart location override for dev #202

mattwelke opened this issue Aug 27, 2024 · 1 comment
Labels
enhancement Enhancement to an existing feature

Comments

@mattwelke
Copy link
Member

Summary

It would be helpful if we could specify a local Helm chart path for the main validator chart when doing local dev. This lets you test changes to the main validator code base without having to release it.

Plugins are harder to do and may be handled later.

Changes in validatorctl:

  • Modify Helm client options so that it can use a local chart path
@mattwelke mattwelke added the enhancement Enhancement to an existing feature label Aug 27, 2024
Copy link

dosubot bot commented Nov 26, 2024

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

Issue Summary:

  • You proposed a feature to specify a local Helm chart path for the main validator during local development.
  • This feature would allow testing changes to the validator code without needing a release.
  • The suggestion involves modifying Helm client options in validatorctl.
  • Handling plugins was noted as a more complex task for future consideration.
  • There have been no comments or further activity on this issue.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of the validatorctl repository by commenting here.
  • If there is no further input, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@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 26, 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 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement to an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants