Kconnect to error when no previous entries exist #343
Description
What happened:
When running 'kconnect to' and 'kconnect to -', a long error message is thrown
What did you expect to happen:
For a simple message to appear that there are no existing entries, perhaps a warning.
How to reproduce it:
Have an empty history.yaml file, and run kconnect to
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
- kconnect version (use
kconnect version): 0.5.2 - Kubernetes version (use
kubectl version): NA - OS (e.g. from
/etc/os-release): All - Target environment (e.g. EKS, AKS, Rancher): NA
- Authentication Used (e.g. SAML, IAM, Azure AD): NA