We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Environment (required):
Describe the bug It is possible to use upctl with resource names. Only problem is that the names are case-sensitive, which is an annoying UX issue.
To Reproduce Steps to reproduce the behavior:
$ upctl network list UUID Name Router Type Zone ────────────────────────────────────── ─────────────────────── ──────── ───────── ───────── 03f20361-e744-4892-acf6-67d1ad1023aa Kubernetes private de-fra1 $ upctl network show kubernetes ERROR: cannot resolve argument: nothing found matching 'kubernetes' $ upctl network show Kubernetes Common UUID: 03f20361-e744-4892-acf6-67d1ad1023aa Name: Kubernetes Router: Type: private Zone: de-fra1 etc etc
Wanted behavior Make name-matching case-insensitive, both in name searches as well as when tab completing (can be completed to correctly cased option)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Environment (required):
Describe the bug
It is possible to use upctl with resource names. Only problem is that the names are case-sensitive, which is an annoying UX issue.
To Reproduce
Steps to reproduce the behavior:
Wanted behavior
Make name-matching case-insensitive, both in name searches as well as when tab completing (can be completed to correctly cased option)
The text was updated successfully, but these errors were encountered: