Add functionality for Automation Tool triggering #20
Labels
Comments
|
I should update the README now, so I can add a section for how to run in an automation tool. |
|
In this branch's commit. Need to test. |
This was referenced Oct 20, 2017
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
Since the UI container can run on its own, and to support scheduled jobs, we can have automation tools like Jenkins run the tester containers against backups.
The tester container will grab all configs needed from the assigned conf.d yaml ONLY! Not even the global yml is needed. I should just add a set of params for an API call to trigger instead of a local container create. All that would be needed is maybe authentication creds and an API endpoint. Lets hope the interface can be made easily.
This also means the transport used will have to also be the transport used for dumping logs. That also needs to be added to the backup specific config.
The text was updated successfully, but these errors were encountered: