Fix aws CLI auto-completions, use smaller kubectl package #924
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
what
aws
auto-completionkubectl
why
aws
CLI is provided in 2 versions, v1 and v2, and which version is in use is managed byupdate-alternatives
. However, each version of the CLI has a corresponding version of theaws_completer
utility to perform auto-completion, but until now, Geodesic always used the v1 completer (a python script), even with the v2 CLI. This mostly worked, but it is not supported or correct.kubectl
package frompackages.cloud.google.com
, which is over 200 MB because it installs multiple versions ofkubectl
. We now install only the latestkubectl
package from the Cloud Posse package repo, which is under 50 MB, to save space. Cloud Posse publishes packages for each minor version ofkubectl
(e.g.kubectl-1.29
) so you can install the latest version compatible with your cluster if you do not want the current latest version.references
This was brought to our attention by aws/aws-cli#8547 since upgrading to Python 3.12 in Geodesic v2.9.0.