Local mounting works for handling backups, ensure that s3 is mounted as well. #24
Labels
Comments
vjeeva
pushed a commit
that referenced
this issue
Oct 23, 2017
* Updated Readme for what we need plus added triggering functionality to UI * Added support for reading remote logs * Saving work of logs based on configs. * Automation tool triggering added, log dumping made for local or s3 based on driver, logs can dump to either and retrieve from either! Also finally routed properly for docker images to load backups via mount rather than ssh tunnel file pipe... Added support for postgres pg_restore parallel restore. Idk if I mmissed anything else * Updated README for leftover items * S3 backups go into host mounted tmp dir * Fix to tmp dir
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably will need to the following architecture.
When fetching a backup, it creates a temp dir on the tester container and stores the file there. Need to copy this into a mounted directory on the HOST MACHINE then mount the same location to the engine container.
Basically right now the postgres driver will fail using s3 due to this, but we NEED this anyways.
The text was updated successfully, but these errors were encountered: