autonomic-cooperative/molecule-hetznercloud
5
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Document volume handling
Some checks failed
continuous-integration/drone/push Build is failing
Details

Browse Source
This commit is contained in:
Luke Murphy 2021-01-06 12:17:20 +01:00
parent 92f645e43d
commit 8e06794f3c
No known key found for this signature in database
GPG Key ID: 5E2EF5A63E3718CC
2 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
CHANGELOG.md
View File

@ -7,9 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased] ## [Unreleased]
- Decolonise Git praxis and use the main branch as default
- Support Python 3.9. - Support Python 3.9.
- Support Molecule 3.2.1 - Support Molecule 3.2.1
- Decolonise Git praxis and use the main branch as default - Add volume creation and clean up handling
## [0.2.2] - 2020-06-15 ## [0.2.2] - 2020-06-15

15
README.md
View File

@ -72,6 +72,21 @@ $ export MOLECULE_NO_LOG=False # not so verbose, helpful
$ export MOLECULE_DEBUG=True # very verbose, last ditch effort $ export MOLECULE_DEBUG=True # very verbose, last ditch effort
``` ```
## Vokume Handling
It is possible to have the driver manage volumes during the test run.
You can add the following stanza to your Molecule configuration to have
Molecule create this volume for the managed VPS. This volume will be cleaned up
after use.
```yaml
volumes:
name: "molecule-hetznercloud-volume-${INSTANCE_UUID}"
size: 11
create: true
```
## Only use `molecule.yml` for configuration ## Only use `molecule.yml` for configuration
It is being worked on that it is possible to remove all the files except the It is being worked on that it is possible to remove all the files except the