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

Kconnect to error when no previous entries exist #343

Open
seankelly001 opened this issue Jul 23, 2021 · 0 comments
Open

Kconnect to error when no previous entries exist #343

seankelly001 opened this issue Jul 23, 2021 · 0 comments
Assignees
Labels
area/history History related issues/prs good first issue Good for newcomers kind/bug Something isn't working priority/backlog Higher priority that awaiting-more-information. This issue is on the backlog for future development.

Comments

@seankelly001
Copy link
Contributor

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
@seankelly001 seankelly001 added kind/bug Something isn't working good first issue Good for newcomers priority/backlog Higher priority that awaiting-more-information. This issue is on the backlog for future development. area/history History related issues/prs labels Jul 23, 2021
@jacobfra jacobfra self-assigned this Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/history History related issues/prs good first issue Good for newcomers kind/bug Something isn't working priority/backlog Higher priority that awaiting-more-information. This issue is on the backlog for future development.
Projects
None yet
Development

No branches or pull requests

2 participants