Short summary
Backing up local GDS logs can be useful for test traceability.
Motivation and user story
When we complete a satellite build and load a final version of the software onto it, it may be useful to have logs of all of the commands and events that came out of the GDS during that process. That way, if we need to audit a final configuration, we have an additional means of doing so.
Proposed implementation
The GDS automagically creates a logs folder in the repo that is gitignored, so it stays on a user's local machine and isn't pushed anywhere. We may want to do something like introduce a make backup-logs that pushes a user's local logs to a private datastore that can be accessed by the team.
Priority
Low
Short summary
Backing up local GDS logs can be useful for test traceability.
Motivation and user story
When we complete a satellite build and load a final version of the software onto it, it may be useful to have logs of all of the commands and events that came out of the GDS during that process. That way, if we need to audit a final configuration, we have an additional means of doing so.
Proposed implementation
The GDS automagically creates a
logsfolder in the repo that is gitignored, so it stays on a user's local machine and isn't pushed anywhere. We may want to do something like introduce amake backup-logsthat pushes a user's local logs to a private datastore that can be accessed by the team.Priority
Low