kubefirst reset should guard against directories and files not being present:
➜ ~ kubefirst version
kubefirst-cli golang utility version: v2.6.0
➜ ~ kubefirst reset
Error: unable to determine contents of kubefirst-checks: unexpected type <nil>
If a detailed error message was available, please make the necessary corrections before retrying.
You can re-run the last command to try the operation again.
➜ ~ rm -rf ~/.k1 ~/.kubefirst
➜ ~ kubefirst reset
Error: unable to determine contents of kubefirst-checks: unexpected type <nil>
If a detailed error message was available, please make the necessary corrections before retrying.
You can re-run the last command to try the operation again.
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Which version of kubefirst are you using?
v2.6.0
Which cloud provider?
None specific
Which DNS?
None specific
Which installation type?
None specific
Which distributed Git provider?
None specific
Did you use a fork of
gitops-template
?No
Which Operating System?
macOS
What is the issue?
kubefirst reset should guard against directories and files not being present:
Code of Conduct