Lazo
Small utility to work with Rancher. It has been developd to be used in CI environments.
Current features:
- get infos on running cluster/project/workload
- get docker image info
- upgrade workload
- execute commands in running containers
Install
$ pip install lazo
or using pipx
$ pipx install lazo
Help
$ lazo --help
Usage: lazo [OPTIONS] COMMAND [ARGS]...
Options:
--version Show the version and exit.
--env
-v, --verbosity verbosity level
-q, --quit no output
-d, --dry-run dry-run mode
--debug debug mode
-h, --help Show this message and exit.
Commands:
docker
rancher
Environment varialbles
- RANCHER_BASE_URL as
--base-url - RANCHER_KEY as
--key - RANCHER_SECRET as
--secret - RANCHER_CLUSTER as
--cluster - RANCHER_PROJECT as
--project - RANCHER_INSECURE as
--inxecure - DOCKER_REPOSITORY as
--repository
You can inspect your default configuration with:
$ lazo --defaults
Env Value Origin
repository https://hub.docker.com/v2
auth
base_url
cluster
insecure False
project
use_names False
or list handler environment variables with:
$ lazo --env
Env Value
DOCKER_REPOSITORY -- not set --
RANCHER_AUTH -- not set --
RANCHER_BASE_URL -- not set --
RANCHER_CLUSTER -- not set --
RANCHER_INSECURE -- not set --
RANCHER_PROJECT -- not set --
RANCHER_USE_NAMES -- not set --
Examples
Rancher
get infos on running workload
$ lazo rancher -i -n info -p cluster1:bitcaster -w bitcaster:bitcaster
Workload infos:
Image: bitcaster/bitcaster:0.3.0a15
Command: ['stack']
imagePullPolicy: Always
upgrading workload
$ export RANCHER_KEY=key
$ export RANCHER_SECRET=secret
$ lazo upgrade saxix/devpi:latest \
--base-url https://rancher.example.com/v3/
--cluster c-wwk6v
--project p-xd4dg
use stdin to read credentials
$ cat .pass.txt | lazo --stdin \
upgrade bitcaster:bitcaster \
bitcaster/bitcaster:0.3.0a10 \
--insecure
execute command in running container
$ lazo shell bitcaster:db -- ls -al /var/log
total 432
drwxr-xr-x 1 root root 4096 Jan 1 01:39 .
drwxr-xr-x 1 root root 4096 Dec 26 00:00 ..
drwxr-xr-x 1 root root 4096 Jan 1 01:39 apt
-rw-r--r-- 1 root root 74886 Jan 1 01:39 dpkg.log
-rw-r--r-- 1 root root 32000 Jan 1 01:39 faillog
drwxr-xr-x 2 root root 4096 May 25 2017 sysstat
Docker
list image available tags
$ lazo docker info saxix/devpi
latest
2.3
2.2
2.1
2.0
1.1
get information on image
$ lazo docker info library/python --filter '3\.6.*alpine3.8' --size
3.6-alpine3.8 26.2MiB
3.6.8-alpine3.8 26.2MiB
3.6.7-alpine3.8 26.2MiB
3.6.6-alpine3.8 26.2MiB
Metadata
Release files for lazo 2.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lazo-2.0.3.tar.gz | 13.4 kB | Without provenance | Details for lazo-2.0.3.tar.gz |
Release files / lazo-2.0.3.tar.gz
| Download URL | lazo-2.0.3.tar.gz |
|---|---|
| Size | 13.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd0f98167ae631fca8665fa184db4395d53409902b0c3530c546bc6aedb7d103
|
|
BLAKE2b-256 checksum How to use checksums |
2e4fa9253b8c8b9d409c0de5b869f585e136e31eefb2a236d220f125e04327e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.2
|
Security for lazo 2.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.