Tooling for manipulating cloud providers (e.g. AWS or Kubernetes) in a CI/CD pipeline
100K+
These images are based on Alpine Linux, and include:
Other useful tools include:
bashcurlgitjqwgetWhere to get help:
Support is only offered to clients of Tiger Computing Ltd
Where to file issues:
https://gitlab.tiger-computing.co.uk/tcl/cloud-tools/issues
Maintained by:
Tiger Computing Ltd
Supported architectures:
amd64
Image source:
GitLab project (history)
This image is designed to be used with a CI/CD system such as GitLab CI. It provides shell commands for the bundled tools that can be invoked by CI/CD jobs. Which of the tools you use and how you use them is entirely down to the project you are using them with.
Each Python tool lives in its own virtualenv under /opt/venvs/ so that
tools with conflicting dependencies (such as cfn-lint and sceptre) can be
installed side by side. Their commands are symlinked into /usr/local/bin,
so they can be run as normal without activating anything.
The python3 and pip on PATH come from the /opt/venvs/default
virtualenv, which contains the Kubernetes Python client. CI jobs can pip install additional packages into it directly. Note that packages installed
this way are not visible to cfn-lint or sceptre; in particular, sceptre runs
Python templates with its own interpreter, which already includes
troposphere.
To add or update a tool, edit the corresponding
venvs/<name>/requirements.txt (or add a new directory to create a new
virtualenv).
Content type
Image
Digest
sha256:200fe0c12…
Size
256.3 MB
Last updated
5 days ago
docker pull tigercomputing/cloud-tools