Tool to enforce ownership and data security within cloud environments
A security and compliance tool for validating your infrastructure.
Using the provided
Dockerfile it is trivial to build a container that contains everyting
necessary to run a the backend, scheduler and worker processes.
The Dockerfile currently supports 3 arguments as
|pip_flags||Used to pass any extra configuration arguments to the pip install command. An example of this could be to pass in the
|extra_packages||Any extra python packages you would like to install, such as custom plugins|
|timezone||The timezone to set in the container, used for the schedulers. Defaults to
The container does not come with a database, that will need to be provided externally. You will also need to map in a volume containing the configuration files
Build with custom plugin from private repository
This example uses the
extra_packages to install a custom plugin
docker build . -t probator:latest --build-arg pip_flags="--extra-index-url https://pypi.company.tld/simple/" --build-arg extra_packages="probator-auth-openid"
To run any part of the system you will need to pass in the configuration folder with the required files (
ssl/private.key) present to
/usr/local/etc/probator inside the container.
The example below will execute the scheduler
docker run --rm -v probator-config:/usr/local/etc/probator probator:latest probator scheduler
The next example shows how to run the API server with a port mapping for a production API server
docker run --rm -p 5000:5000 -v probator-config:/usr/local/etc/probator probator:latest gunicorn -w 6 -b 0.0.0.0:5000 -k gthread -t 60 "probator.wsgi:run()"
Based on the work by Riot Games' Cloud Inquisitor
Release history Release notifications
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size probator-1.3.0.tar.gz (89.4 kB)||File type Source||Python version None||Upload date||Hashes View hashes|