search

upbound / up

The @upbound CLI
Apache License 2.0
51 stars 41 forks source link

Automatic API Token Generation in UP CLI for up ctp connect and kubeconfig Commands #408

Closed haarchri closed 1 month ago

haarchri commented 7 months ago

What problem are you facing?

After successfully logging in using up login, it's reasonable to expect that further authentication for related commands would be handled automatically. The necessity to manually generate and provide an API token for up ctp connect and up ctp kubeconfig commands is a step that could be optimized.

In comparison, CLI tools from public cloud providers like AWS and Azure offer a more streamlined approach. For instance, AWS CLI's aws eks update-kubeconfig --region eu-central-1 --name test and Azure CLI's az aks get-credentials --resource-group test --name test do not require manual API token input post-login. These commands handle necessary authentications internally, leveraging the initial login credentials, which is significantly more user-friendly and efficient.

How could Upbound help solve your problem?

I'd like to suggest an enhancement for the UP CLI, specifically concerning the up ctp connect and up ctp kubeconfig commands. Currently, these commands require the use of the --token flag to provide an API token. However, this requirement seems redundant and inconvenient, given that users are already authenticated through up login.

Epic #

djeremiah commented 5 months ago

Is this a dupe of #338?

haarchri commented 1 month ago

all possible now with up ctx