datumctl doesn't support colon separated file listings in the KUBECONFIG variables #47
Description
What task were you trying to complete?
Using datumctl
Describe the usability issue
The datumctl utility can't handle parsing KUBECONFIG if it uses colon-separated file listings. It interprets the entire string as a path, resulting in files with colons in their name.
Why was this confusing or difficult for you?
kubectl can do this and having multiple files in KUBECONFIG is a way that power users manage multiple kubeconfigs on a system.
Here's a link to their docs where they discuss using the functionality: https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#append-home-kube-config-to-your-kubeconfig-environment-variable
What did you expect to happen instead? (Optional)
I expected datumctl to interact with my KUBECONFIG variable like kubectl does.
Do you have any suggestions for improvement? (Optional)
No response
Relevant URL or Section of the Application (Optional)
No response
Attachments / Screenshots (Optional)
No response