Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

option to ignore download paths #140

Closed
bernhardreiter opened this issue May 18, 2022 · 4 comments
Closed

option to ignore download paths #140

bernhardreiter opened this issue May 18, 2022 · 4 comments

Comments

@bernhardreiter
Copy link
Member

A user wants to configure advisory paths that are ignored to for downloading, checking and aggregating.

Two motivations:

  1. Avoid error messages for paths that are advertised, but not accessible, e.g. TLP:AMBER where I do not have access.
  2. Ignore advisories I do not want.

Especially if the downloading is repeated, like an everyday run of the aggregator, the error message are unhelpful. It is similiar if the checker or the downloader are run as part of a repeating process.

@bernhardreiter
Copy link
Member Author

technical considerations

It may make sense to allow specifying a pattern or several patterns somehow.

@JanHoefelmeyer JanHoefelmeyer added this to the Release 2.4.0 milestone Jul 7, 2023
@JanHoefelmeyer
Copy link
Contributor

These options need to be configurable via a config file and as command line parameters.

@JanHoefelmeyer
Copy link
Contributor

The currently open PRs implement the following functionalities:

Via a TOML file or via command line parameters, a slice of Regular Expressions can be given unto the ignorepattern option, which will cause the tool to ignore all files whose path contain any of these patterns.

#419 ( Downloader: ignore advisories by given patterns #419 ) implements this for the csaf_downloader

#420 ( Checker: ignore advisories by given patterns #420 ) implements this for the csaf_checker

#421 ( Downloader: ignore advisories by given patterns #421 ) implements this for the csaf_aggregator

Due to the nature of these checks, entire directories as well as singular files can be excluded from all three tools. This should solve the issue.

@s-l-teichmann
Copy link
Contributor

This is resolved by #419 #420 and #421

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants