solo deployment create should use the context and cluster provided for where to save the remote config instead of using the k8s current context

[jeromy-cannon]

kind create cluster -n solo
rm -Rf ~/.solo
solo init
kubectx

kubectx output (kind-solo is current context):

docker
docker-desktop
gke-edge
gke-fullstack
gke-jeromy
gke-secure
kind-solo
re-lat

solo context connect -n jeromy-solo --context gke-fullstack --cluster-name gke_hedera-automation_us-central1_fullstack-test-edge

prompts me for email address, but, I can't supply it via a flag.
then asks: Enter the Solo deployment cluster names (comma separated), even though I already gave it.

solo deployment create -n jeromy-solo --deployment-clusters gke_hedera-automation_us-central1_fullstack-test-edge --context-cluster gke-fullstack=gke_hedera-automation_us-central1_fullstack-test-edge

******************************* Solo *********************************************
Version			: 0.99.0
Kubernetes Context	: kind-solo
Kubernetes Cluster	: kind-solo
Kubernetes Namespace	: jeromy-solo
**********************************************************************************
(node:14104) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✔ Initialize [7s]
  ✔ Acquire lease - lease acquired successfully, attempt: 1/10
↓ Prompt local configuration
✔ Validate cluster connections [0.5s]
  ✔ Testing connection to cluster: gke-fullstack [0.5s]
✖ Failed to read remote config from cluster
*********************************** ERROR *****************************************
failed to read existing leases, unexpected server response of '500' received
***********************************************************************************

looks like it isn't switching clusters, might be a missed requirement.