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.
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.