tgonzales114 / drum

Disconnected RPM Update Manager

drum

Disconnected RPM Update Manager

drum's Issues

tool to generate expected log files

Currently there isn't a tool to generate the expected log files needed to run drum.
drum expects files in the following format:

template

/var/log/example-data/<DATE_ISO-8601>/<REPOSITORY>.txt

example

/var/log/drum/2024-07-21/baseos.txt

where the content in each log file is the full path of all rpms for that repository on that day.

template

/path/to/file1.rpm
/path/to/file2.rpm
/path/to/file3.rpm
...

example

/data/repositories/baseos/Packages/c/coreutils-8.30-15.el8.x86_64.rpm
/data/repositories/baseos/Packages/k/kernel-4.18.0-553.8.1.el8_10.x86_64.rpm
/data/repositories/baseos/Packages/s/sudo-1.9.5p2-1.el8_9.x86_64.rpm
...

These files would need to be generated for each repository every day, and they would need to run after any jobs that may be mirroring these repositories.

drum should be able to take arguments

drum should be able to take arguments passed to the command rather than only being able to run interactively.
Potential arguments that could be made:

short-flag/long-flag - purpose of argument
-d/--days - number of days to go back as the start
-s/--start - the date to use as the start
-r/--repos - list of repositories to use
-z/--compress - whether or not to compress the output file
-Z/--compression - the compression tool to use when compressing the output file

tool to deploy output file

Currently there isn't a tool to deploy the output file.
The output file would just need to be decompressed and unarchived at the proper location, but if not done properly could lead to nested data that may be confusing to clean up.