Add generate_secrets functionality
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
This commit is contained in:
14
README.md
14
README.md
@ -8,17 +8,23 @@ This is meant to be used as a [Drone plugin](http://plugins.drone.io/).
|
||||
|
||||
## Settings
|
||||
|
||||
### With defaults
|
||||
### Required (no default)
|
||||
|
||||
- **deploy_key**: SSH private key part for ssh public key authentication
|
||||
- **stack**: Name of the stack to be deployed
|
||||
|
||||
### Optional (with defaults)
|
||||
|
||||
- **compose** (default: `compose.yml`): compose file to use for deploying
|
||||
- **host** (default: `swarm.autonomic.zone`): Host to deploy to (don't include `ssh://`)
|
||||
- **port** (default: `222`): SSH port to connect to
|
||||
- **user** (default: `drone`): System user to connect via SSH with
|
||||
|
||||
### Without defaults
|
||||
### Dangerous options, unwise outside CI
|
||||
|
||||
- **deploy_key**: SSH private key part for ssh public key authentication
|
||||
- **stack**: Name of the stack to be deployed
|
||||
- **generate_secrets** (default: no): randomly set all `secrets:` found in the
|
||||
compose file -- you won't be able to retrieve them afterwards, so you almost
|
||||
certainly don't want this for real deployments.
|
||||
|
||||
## Example
|
||||
|
||||
|
Reference in New Issue
Block a user