What problem does this feature solve? Please describe.
Mazer currently knows what content is installed, and when that version was installed, but it doesn't
track any info about what happened before the current state.
For example, what version of a collection was installed prior to the update.
Or what collections and content were installed at the same time.
Note: This wouldn't need to be a transactional log, that could be rolled back and replayed. This would be for audit and troubleshooting purposes.
Proposed Solution
Possibilities:
A history file or db in ~/.ansible/content that records all the changes. Could be json, etc.
Downside would be difficulties in dealing with concurrent changes.
In the .galaxy_install_info, instead of only recording the current state, make the file a ordered list of transactions.
Downside would be the files could get large.
Alternatives
Describe alternatives you've considered
Just store the content path in a git repo and commit after every transaction.
Feature Request
Use Case
What problem does this feature solve? Please describe. Mazer currently knows what content is installed, and when that version was installed, but it doesn't track any info about what happened before the current state.
For example, what version of a collection was installed prior to the update. Or what collections and content were installed at the same time.
Note: This wouldn't need to be a transactional log, that could be rolled back and replayed. This would be for audit and troubleshooting purposes.
Proposed Solution
Possibilities:
A history file or db in ~/.ansible/content that records all the changes. Could be json, etc. Downside would be difficulties in dealing with concurrent changes.
In the .galaxy_install_info, instead of only recording the current state, make the file a ordered list of transactions. Downside would be the files could get large.
Alternatives
Describe alternatives you've considered