Go automation at hospital
Below are the activities to be able to perform via GO.
Upgrade
Upgrade the platform (to be used under directions from technical team)
Deploy
Deploy everything or just the configuration to a particular environment, flexibility to deploy on pre-prod and prod.
Operate
(background) Take backup from passive to a well known location or configuration provided by the user
Clear http cache
Prepare production logs on demand. These logs are published as an artefact in Go after the job finishes.
Switch from active to passive
[TO DO LATER] Periodically delete orphan images uploaded (applicable to JSS, script not available yet for this)
Implementation Support
Task to be triggered manually. Extract database dump, anonymise and publish the link.
Same as above except publish an empty database.
Do not publish the anonymised database dump as an artifact from Go because of the size. the dump should be served from the passive server. The link should be exposed via apache httpd on passive. The link addition should be done via puppet.
Define pipelines in QA environment (e.g. .6) running at TW to be able to use the dump copied at a particular file location to apply it to QA environment