* Change the go module path
from github.com/csaf-poc/csaf_distribution to github.com/gocsaf/csaf.
* Rename archive for release tarballs.
* Adjust testing scripts and documentation.
* use `csaf_distribution` with an underscore as underscores
are allowed by RFC9110 and it is more consistent as it is used
with underscore at other places.
* change example to `VERSION` to indicate that this is dynamic.
* 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>
* 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
* Remove verbose flag from downloader.
* Do structured http logging in forwarder, too.
* Use structured logging to separate http traffic of downloader from forwarder.
* started with forwarding support in downloader
* Add missing files.
* Add missing files.
* Raise needed Go version
* More Go version bumping.
* Fix forwarding
* Go 1.21+ needed
* Make terminating forwarder more robust.
* Better var naming
* Remove dead code. Improve commentary.
* Prepare validation status adjustment.
* Move validations to functions to make them executable in a loop.
* Introduce validation mode flag (strict, unsafe)
* Make uploader use the TOML config file intrastructure, too.
* Improve method naming a bit.
* Improve method naming a bit.
* Add forgotten struct tags for TOML
* Add version to command line only parameters in uploader documentation
* Be explicit about supported options in config file.
* allow interactive flags in config file.
---------
Co-authored-by: JanHoefelmeyer <Jan Höfelmeyer jhoefelmeyer@intevation.de>
* Label the option experimental and limited at all places.
* Point to the downloader documentation as single point to write more.
* Add more hints on how the old PEM block encryption is experimental
and why it often shall not be used.
---------
Co-authored-by: JanHoefelmeyer <hoefelmeyer.jan@gmail.com>
Co-authored-by: Bernhard Reiter <bernhard@intevation.de>
* Adapt finding the current go version to the new result of https://go.dev/VERSION\?m=text by using only the first line.
Co-authored-by: JanHoefelmeyer <hoefelmeyer.jan@gmail.com>
