mirror of https://gitlab.com/psuapp/psu.git synced 2024-08-30 18:12:34 +00:00

Go to file

Prior to this pull request `psu` script act like this:
Stack env vars are set in the `deploy()` function. When a new stack is deployed it gets no env vars, and when an existing one is updated its envvars are reused (extracted from its stack definition into the stack_envvars variable and set back again).

For the first case this pull request load the content of the env vars file and transform it into JSON using a `jq` command and set it as the `stack_envvars` value.
For the second case, though, the script update the current stack env vars rather than setting them from scratch, keeping any value not previously set in the env file.

The environment variables file path is customizable with the environment variable `$ENVIRONMENT_VARIABLES_FILE` or the `-g` flag, like this:
```bash
export ACTION="deploy"
export PORTAINER_USER="admin"
export PORTAINER_PASSWORD="password"
export PORTAINER_URL="http://portainer.local"
export PORTAINER_STACK_NAME="mystack"
export DOCKER_COMPOSE_FILE="/path/to/docker-compose.yml"
export ENVIRONMENT_VARIABLES_FILE="/path/to/env_vars_file"

./psu
```

Or with flags:
```bash
./psu -a deploy -u admin -p password -l http://portainer.local -n mystack -c /path/to/docker-compose.yml -g /path/to/env_vars_file
```

close #7

2019-05-10 16:33:49 +02:00

Dockerfile

Change Docker entrypoint to /usr/local/bin/psu

2018-11-26 19:24:14 -05:00

LICENSE

Add license

2018-11-21 15:12:03 -05:00

psu

Add custom stack environment variables

2019-05-10 16:33:49 +02:00

README.md

Fix relative links in docs

2018-12-29 10:44:59 -08:00

README.md

Portainer Stack Utils

Bash script to deploy/update/undeploy stacks in a Portainer instance from a docker-compose yaml file. Based on previous work by @vladbabii on docker-how-to/portainer-bash-scripts.

Supported Portainer API

Script was created for the latest Portainer API, which at the time of writing is 1.9.2.

How to install

Just clone the repo and use the script

git clone https://github.com/greenled/portainer-stack-utils.git
cd portainer-stack-utils
./psu ...

Requirements

You will need these dependecies installed:

For Debian and similar apt-powered systems: apt install bash httpie jq.

How to use

The provided psu script allows to deploy/update/undeploy Portainer stacks. Settings can be passed through envvars and/or flags. Both envvars and flags can be mixed but flags will always overwrite envvar values. When deploying a stack, if it doesn't exist a new one is created, otherwise it's updated (unless strict mode is active).

With envvars

This is particularly useful for CI/CD pipelines.

ACTION ("deploy" or "undeploy", required): Whether to deploy or undeploy the stack
PORTAINER_USER (string, required): Username
PORTAINER_PASSWORD (string, required): Password
PORTAINER_URL (string, required): URL to Portainer
PORTAINER_STACK_NAME (string, required): Stack name
DOCKER_COMPOSE_FILE (string, required if action=deploy): Path to doker-compose file
PORTAINER_PRUNE ("true" or "false", optional): Whether to prune unused containers or not. Defaults to "false".
PORTAINER_ENDPOINT (int, optional): Which endpoint to use. Defaults to 1.
HTTPIE_VERIFY_SSL ("yes" or "no", optional): Whether to verify SSL certificate or not. Defaults to "yes".
VERBOSE_MODE ("true" or "false", optional): Whether to activate verbose output mode or not. Defaults to "false". See verbose mode below.
DEBUG_MODE ("true" or "false", optional): Whether to activate debug output mode or not. Defaults to "false". See debug mode below.
STRICT_MODE ("true" or "false", optional): Whether to activate strict mode or not. Defaults to "false". See strict mode below.

Examples

export ACTION="deploy"
export PORTAINER_USER="admin"
export PORTAINER_PASSWORD="password"
export PORTAINER_URL="http://portainer.local"
export PORTAINER_STACK_NAME="mystack"
export DOCKER_COMPOSE_FILE="/path/to/docker-compose.yml"

./psu

export ACTION="undeploy"
export PORTAINER_USER="admin"
export PORTAINER_PASSWORD="password"
export PORTAINER_URL="http://portainer.local"
export PORTAINER_STACK_NAME="mystack"

./psu

With flags

This is more suitable for standalone script usage.

-a ("deploy" or "undeploy", required): Whether to deploy or undeploy the stack
-u (string, required): Username
-p (string, required): Password
-l (string, required): URL to Portainer
-n (string, required): Stack name
-c (string, required if action=deploy): Path to doker-compose file
-r ("true" or "false", optional): Whether to prune unused containers or not. Defaults to "false".
-e (int, optional): Which endpoint to use. Defaults to 1.
-s ("yes" or "no", optional): Whether to verify SSL certificate or not. Defaults to "yes".
-v ("true" or "false", optional): Whether to activate verbose output mode or not. Defaults to "false". See verbose mode below.
-d ("true" or "false", optional): Whether to activate debug output mode or not. Defaults to "false". See debug mode below.
-t ("true" or "false", optional): Whether to activate strict mode or not. Defaults to "false". See strict mode below.

Examples

./psu -a deploy -u admin -p password -l http://portainer.local -n mystack -c /path/to/docker-compose.yml

./psu -a undeploy -u admin -p password -l http://portainer.local -n mystack

Verbose mode

In verbose mode the script prints execution steps.

Getting auth token...
Getting stack mystack...
Stack mystack not found.
Getting Docker info...
Getting swarm cluster (if any)...
Swarm cluster found.
Preparing stack JSON...
Creating stack mystack...

Verbose mode can be enabled through VERBOSE_MODE envvar or -v flag.

Debug mode

In debug mode the script prints as much information as possible to help diagnosing a malfunction.

WARNING: Debug mode will print configuration values (with Portainer credentials) and Portainer API responses (with sensitive information like authentication token and stacks environment variables). Avoid using debug mode in CI/CD pipelines, as pipeline logs are usually recorded.

Debug mode can be enabled through DEBUG_MODE envvar or -d flag.

Strict mode

In strict mode the script never updates an existent stack nor removes an unexistent one, and instead exits with an error.

Strict mode can be enabled through STRICT_MODE envvar or -t flag.

License

Source code contained by this project is licensed under the GNU General Public License version 3. See LICENSE file for reference.