ALBS-901: New service albs-oval-errata-dif #1
No reviewers
Labels
No Label
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kzhukov/albs-oval-errata-diff#1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ALBS-901"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -0,0 +30,4 @@
```bash
$ pip install -r requirements.txt
```
4. Create config file using [config.default.yml](config.default.yml) and start service with _albs_oval_errata_diff.py_ script
Extra whitespaces between
start
andservices
@ -0,0 +77,4 @@
issued_dt = datetime.datetime.strptime(issued, "%Y-%m-%d")
# we are only interesed in Security advisories after RHEL 8.3
if ('RHSA' not in title and 'ALSA' not in title) or issued_dt < not_before:
It's rare, but security advisories can also be RHBAs or RHEAs. Up to you if want to add this to the logic, nothing against merging this as it is now.
As a tip, [RH|AL]BAs and [RH|AL]EAs that became security advisories must have the severity field set to any of the valid values, these are: Low, Moderate, Important or Critical. You can check them here https://access.redhat.com/security/updates/classification
Thanks for heads up
I created task for adding support of BA/EA in https://cloudlinux.atlassian.net/browse/ALBS-915
I will work on this feature in separate branch. This one I will merge
@ -0,0 +12,4 @@
# DEFAULTS
DIFF_FILE = Path('/tmp/albs-oval-errata-diff.json')
Not sure if we want to add a timestamp or the like to both the diff and log files. As my previous comment, anything against merging this as it is
Not sure what you mean. There are no timestamps in diff file. Only timestamps of report generation date and timestamp of oldest SA we are looking for
Oh okay, I see there's a timestamp in the report ????
Left a few minor comments. But overall it looks good to me. Just one question, why using a personal repo rather than a communiy one?
We discussed this at the end of the year, and desided not to publish this due to political reasons)
@Korulag am I right?