* docs: move link to final CSAF 2.0 in README
* docs: underline that we are _not_ offering an API yet
* Grammar fix
---------
Co-authored-by: JanHoefelmeyer <hoefelmeyer.jan@gmail.com>
* Convert a lot of variables to snake case
* Add snakecase for variables made out of two words that had it in no version yet (for consistency)
* Adjust example files too
---------
Co-authored-by: JanHoefelmeyer <hoefelmeyer.jan@gmail.com>
* move csaf_searcher to a lower prio place
* Adjust wording
* Grammar fix #2 'this is work in progress' -> 'This is a work in progress'...
---------
Co-authored-by: JanHoefelmeyer <hoefelmeyer.jan@gmail.com>
* docs: improve timerange documentation
* add a documentation section to the downloader docs for the
timerange-option.
* point aggregator and checker docs to the downloader section for
timerange.
* docs: use a better example for timerange minutes
* use full name for printing out the used logfile for the downloader.
* for debug or verbose, log the timeintervall that will be used
for downloader and aggregator. (The checker has this as part
of its output already.)
* Simplify forward method
* Add unit test for validation status
* Add unit test for stats logging in forwarder.
* Add unit test for http client creation.
* Add unit test for replaceExt
* Add unit test for buildRequest
* Add unit test for limitedString
* Add unit test for storeFailedAdvisory
* Add unit test for storeFailedAdvisory ... fixed
* Add unit test for storeFailed
* Add unit test for forward
* comment wording
* Change release action to use elder Ubuntu runner
* use `ubuntu-20.04` so we get binaries that are more
compatible with elder GNU/Linux distribution, because
go binaries link to glibc (for some operating system operations
like dns).
resolve #456
* docs: update main README
* introduce more structure and put commands for users to the top.
* improve description of the command for the 3.0 release.
* Add 'Tools for ...' to make it more readable.
---------
Co-authored-by: Sascha L. Teichmann <sascha.teichmann@intevation.de>
* Remove verbose flag from downloader.
* Do structured http logging in forwarder, too.
* Use structured logging to separate http traffic of downloader from forwarder.
