-
-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR & Release management maintenance #940
Conversation
152ff29
to
10688e8
Compare
Type "# It ships with common commands like `terraform`" Enter | ||
Sleep 500ms | ||
|
||
Type "terraform -help" Enter | ||
Sleep 500ms | ||
|
||
Type "# ...and the `aws` CLI =)" Enter | ||
Sleep 500ms | ||
|
||
Type "aws help" Enter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What can we showcase then that make it more than jq
. Not that it was awe-inspiring in the previous version, this is definitely less.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we at least bundle atmos
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IDK. I took out Terraform in favor of having the option to use Tofu, and aws
in preparation for the cloud-agnostic version of Geodesic. Really kubectl
is the biggest thing left, and after that, it is mostly the scripts, prompt, integration, etc. that make Geodesic wonderful. It is great that we have a robust set of tools, but they mostly follow the Unix preference of doing one thing well and being composable, so not flashy on their own.
I suppose we could ls /usr/local/bin
, which is empty on debian-slim
.
2to3@ docs* pip3.12*
2to3-3.12* eks-update-kubeconfig* pydoc@
annotate-namespace* eks-update-kubeconfig.draft* pydoc3@
args* emailcli@ pydoc3.12*
awless@ geodesic-aptindex-md5* python@
aws@ git-credential-github* python-config@
aws-config-setup* goofys@ python3@
aws-region* grafana-db* python3-config@
aws2@ helm3-metadata-fix* python3.12*
aws2_completer@ helmctl* python3.12-config*
aws_completer@ idle@ s3*
boot* idle3@ session-manager-plugin@
build-kops-manifest* idle3.12* short.txt
build-kubecfg* init* terminal-server
cfssl@ install-docker-command* tfenv@
codefresh-pipeline* kopsctl* tfmask@
codefresh-settings* kubectl-auto-select* tmate-session*
conf-directory* make* to_short.txt
confirm* new-project* twiddle*
crudini* no-arm64-support* wheel*
deps* pip* wrapper*
destroy-namespace* pip3* yaml-diff*
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The important thing is that I got vhs
working again. You can update the demo whenever you feel inspired.
I do not want to install Atmos, because that triggers the Atmos integrations, which will not work in the demo environment (no stacks, no components).
It is kind of ironic that we install about 60 packages and still do not have an easy way to show the power of Geodesic, but in reality, the advantage is we have done all the work to curate, install, and integrate the packages. Plus, as I said before, all the integrations, particularly with Kubernetes (Helm, Helm plugins, Kubeprompt, etc.) and AWS, like assuming roles and connecting to EKS clusters. All hard to show off on a demo running without any code, configuration, or credentials.
what
vhs-action
in a separate stepalpine-only
why
install-fonts
invhs-action
boto3
release notes are huge and yet not very informativereferences