Retain data beyond VM life
AgentCormac opened this issue · 3 comments
As alluded to in previous issues:
-Reinstalls after machine restart
-Make postgres_data_dir configurable via variable
This role does not allow you to retain AMX data and configuration. Need to be able to retain data beyond the life of the VM. Using Ansible is all about slash and burn environments, build and env, inject data etc.
This is especially an issue when running AWX with Vagrant and VirtualBox. I would like to be able to map the DB directory to a share on the host and for the (host resident) DB not to be wiped when the VM is recreated.
OR
How do I extract data and then re-inject it when the VM is rebuilt?
The backup.yml and restore.yml file mentioned in the Tower documentation do not seem to exist.
Copying the DB files seems to corrupt the DB (suspect key/certificate issue).
Changing the DB location as Pull Request #4 postgres_data_dir in a variable retains data during reboots but overwrites the data on rebuild.
Is anyone maintaining this role? It doesnt look like it has been updated in a while.
Did you manage to find a solution to the fact that "the backup.yml and restore.yml file mentioned in the Tower documentation" do not actually exist?
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.