| Crates.io | loopy |
| lib.rs | loopy |
| version | 0.1.0 |
| created_at | 2023-03-28 15:33:31.487643+00 |
| updated_at | 2023-03-28 15:33:31.487643+00 |
| description | Kubernetes packaging inner feedback loop. |
| homepage | https://github.com/salt-labs/loopy |
| repository | |
| max_upload_size | |
| id | 823179 |
| size | 1,587,405 |
A Kubernetes packaging helper utility that tries to prevent you from going loopy.
It's useful for those times when you find yourself testing the same inner loop like repeatedly installing and upgrading the same set of Helm charts on a kind cluster after only a couple lines of changes to a values file.

loopy is available with cargo.cargo install loopy
Once you have loopy installed, there are couple of things you need to do to get up and running.
# Where you want to store your loopy configuration.
LOOPY_HOME="${HOME}/loopy"
# Create the folder structure.
mkdir --parents "${LOOPY_HOME}/config/{capi,helm,manifests,carvel}"
cd "${LOOPY_HOME}"
loopy.yaml# If you need a starter sample.
curl --output "${LOOPY_HOME}/loopy.yaml" https://raw.githubusercontent.com/salt-labs/loopy/trunk/config/loopy.yaml
vim loopy.yaml
If you need a kind cluster for local testing, there is a sample configuration in the config/capi/kind directory with usage instructions in the kind section.
Before continuing, ensure you are connected to the cluster.
kubectl cluster-info
loopy --help
loopyloopy --config loopy.yaml --action install
loopy again to clean up.loopy --config loopy.yaml --action uninstall
If you don't already have the dependencies installed, loopy will ask to install them for you if you are internet connected.
Once that's done you can add the vendor folder to the PATH of your current shell and go from there.
export PATH=$(pwd)/vendor:$PATH