Implement solo context use - updates the LocalConfig by connecting a deployment to a k8s context

[jeromy-cannon]

• solo context use --context kind-solo --cluster kind --namespace solo-1
  • The context use subcommand is to create a mapping of the Kubernetes context provided to a cluster that should be present when connecting to that context.
  • --context kind-solo - the CONTEXT_NAME for kubectl config use-context CONTEXT_NAME
  • --cluster kind-solo - the cluster name to set in the LocalConfig
  • --namespace solo-1 - if the namespace is provided it will be used to update or create a deployment in the LocalConfig assigning the cluster provided

Tasks

Beta Give feedback

1. When solo context use --quiet is invoked, then contextName will default to the current k8s context
2. When solo context use is invoked, the user will be prompted to supply a contextName, will default to the current k8s context, and supply a list for the user to choose from based on the values in their kube config
3. When solo context use --quiet is invoked, then clusterName will default to the clusterName of the cluster connected when connecting to the current k8s context
4. When solo context use is invoked, the user will be prompted to supply a clusterName
5. When solo context use --quiet is invoked, then namespace will default to the current k8s default namespace
6. When solo context use is invoked, the user will be prompted to supply a namespace, it will default to the current k8s default namespace
7. When solo context use --context <context-name> is invoked, then contextName will be set to the passed in by the user
8. When solo context use --cluster <cluster-name> is invoked, then clusterName will be set to the passed in by the user
9. When solo context use --namespace <namespace> is invoked, then namespace will be set to the passed in by the user
10. When solo context use is invoked, then the deployment will be retrieved from the LocalConfig deployments Map using the namespace and a Deployment is returned then set the LocalConfig currentDeploymentName to the namespace
11. When solo context use is invoked, then the deployment will be retrieved from the LocalConfig deployments Map using the namespace and null is returned then do not set the LocalConfig currentDeploymentName
12. When solo context use is invoked, then the clusterName value will be retrieved from the LocalConfig contextMappings map using the contextName, if this matches the clusterName supplied to the CLI do nothing
13. When solo context use is invoked, then the clusterName value will be retrieved from the LocalConfig contextMappings map using the contextName, if null is returned, add a new mapping to contextMappings using the contextName and clusterName supplied to the CLI
14. When solo context use is invoked, then the clusterName value will be retrieved from the LocalConfig contextMappings map using the contextName, if the value does not match the clusterName supplied to the CLI prompt the user providing them with the values provided by the CLI and the previously saved clusterName, asking the user if they want to override with the supplied clusterName, then override or not based on their response
15. When solo context use --force is invoked, then the clusterName value will be retrieved from the LocalConfig contextMappings map using the contextName, if the value does not match the clusterName supplied to the CLI then override the clusterName with the one supplied to the CLI
16. When any changes are made to LocalConfig, then the changes will be persisted to the file system

• depends on Create a Local Config for storing configurations on the users machine #590