Some more commands for AWS and Kubernetes SHOW_ON_COMMAND

[polothy]

Just added a few more CLI tools to my config and thought I'd share if you are interested:

typeset -g POWERLEVEL9K_KUBECONTEXT_SHOW_ON_COMMAND='kubectl|helm|kubens|kubectx|oc|istioctl|kogito|k9s|jx|eksctl|helmfile|kops|tkn'
typeset -g POWERLEVEL9K_AWS_SHOW_ON_COMMAND='aws|awless|terraform|pulumi|cdk|terragrunt|sam|jx|eksctl|kops'

Info on the tools:

• k9s - a terminal UI for kubernetes
• jx - Jenkins X - a pipeline runner in kubernetes. As the project evolves, it may not make sense in the AWS variable.
• eksctl - the official CLI for AWS EKS (Kubernetes).
• helmfile - a popular way to manage Helm chart installs
• kops - Kubernetes Operations (official Kubernetes tool for installing and managing a kubernetes cluster)
• tkn - Tekton CLI - a Kubernetes pipeline project from Google
• cdk - AWS CDK project, deploys things into AWS like Terraform, Pulumi, etc.
• terragrunt - wraps Terraform
• sam - AWS SAM CLI, deploys serverless things into AWS.

Also, just want to add, I upgraded from 1.7 to 1.12 of p10k, and wow... amazing updates. The Instant prompt, Show on command and Transient prompt are all magical. I didn't know how much I wanted those! Really amazing work, just wanted to say thank you!

[romkatv]

Thanks for the list!

Which of these tools would also make sense to include in POWERLEVEL9K_GOOGLE_APP_CRED_SHOW_ON_COMMAND and POWERLEVEL9K_AWS_SHOW_ON_COMMAND? Both of them currently include terraform, so I guess at least terragrunt should apply? What else?

And what about POWERLEVEL9K_GCLOUD_SHOW_ON_COMMAND? Do any of these tools respect ~/.config/gcloud?

[polothy]

For Azure:

• jx
• terragrunt

For Google Cloud

• kops
• jx
• terragrunt

[romkatv]

For Azure:

• jx
• terragrunt

Thanks!

For Google Cloud

• kops
• jx
• terragrunt

Is this for gcloud segment or for google_app_cred?

• gcloud shows google cloud cli account and project. The standard tool that's affected by what gcloud prompt shows is also called gcloud.
• google_app_cred shows credentials (https://cloud.google.com/docs/authentication/production). There is no standard tool that uses these credentials. All tools that use Google Cloud API implicitly use credentials.

[polothy]

Hrm, really sorry, I don't actually use Google Cloud, so this isn't really making sense to me. But... all three of these tools would need to authenticate to Google Cloud and also make resources in Google Cloud. Not sure if that helps 😕

[romkatv]

Your reply indicates that there might be misunderstanding about the list of commands that are appropriate to list in POWERLEVEL9K_KUBECONTEXT_SHOW_ON_COMMAND. Those and only those commands must be listed there whose behavior is affected by the current kubernetes context as set by kubectl config set-context ... and as reported by kubectl config current-context. If a command uses kubernetes but its behavior is not affected by the current context as defined above, it must not be listed in POWERLEVEL9K_KUBECONTEXT_SHOW_ON_COMMAND.

Is the behavior of eksctl affected by the current kubernetes context as defined above? What about jx? What about other commands?

The same goes for POWERLEVEL9K_AWS_SHOW_ON_COMMAND. Only commands that read and respect AWS_VAULT, AWSUME_PROFILE, AWS_PROFILE, or AWS_DEFAULT_PROFILE environment variable must be on the list. Does eksctl respect any of these variables?

[polothy]

Yeah, eksctl should behave similarly to aws CLI, but it also talks to Kubernetes clusters in AWS, so it belongs in both AFAIK.

If these are too controversial, no worries, they were just suggestions. I was able to easily configure the lists myself for the tools I use.

If I were to rate things on how likely someone else would actually be using them (this is highly subjective), they would be:

• sam
• cdk
• helmfile

[romkatv]

Sorry for the long delay.

Yeah, eksctl should behave similarly to aws CLI, but it also talks to Kubernetes clusters in AWS, so it belongs in both AFAIK.

eksctl must be listed in POWERLEVEL9K_KUBECONTEXT_SHOW_ON_COMMAND if and only if it respects the current context as specified in ~/.kube/config. If it talks to Kubernetes clusters but does not read ~/.kube/config or does not respect the current context specified in that file, it must not be listed in POWERLEVEL9K_KUBECONTEXT_SHOW_ON_COMMAND.

Does eksctl respects the current context specified in ~/.kube/config?

If these are too controversial

"Controversial" isn't the right word. I want POWERLEVEL9K_KUBECONTEXT_SHOW_ON_COMMAND to list all commands that respect the current context as specified in ~/.kube/config. There is no judgement involved. Either a command respects the current context as specified in ~/.kube/config or it doesn't.

The same goes for POWERLEVEL9K_AWS_SHOW_ON_COMMAND. Those and only those commands that read and respect AWS_VAULT, AWSUME_PROFILE, AWS_PROFILE, or AWS_DEFAULT_PROFILE environment variable must be on the list.

Does eksctl read and respect AWS_VAULT, AWSUME_PROFILE, AWS_PROFILE, or AWS_DEFAULT_PROFILE environment variable?

[maximbaz]

• k9s uses $KUBECONFIG so I'd add it to where kubectl currently is defined
• terragrunt is a thin wrapper over terraform, so add it where terraform is currently set

the rest I never heard of, but some quick notes:

• helmfile has apply subcommand which modifies k8s cluster, I'd imagine it is a wrapper over helm, so add it to where helm is
• after a quick search, kops and eksctl seem to be able to generate kubeconfig, but I'm not sure if they actually rely on it

I'd wait for comments from people who actually used these and the rest of the tools

[romkatv]

Thanks, @maximbaz !

I've added k9s|helmfile to POWERLEVEL9K_KUBECONTEXT_SHOW_ON_COMMAND and terragrunt to POWERLEVEL9K_{AWS,AZURE,GOOGLE_APP_CRED}_SHOW_ON_COMMAND.