Merge ~pfsmorigo/ubuntu-cve-tracker:pfsmorigo/pocket_field_for_publish_cves into ubuntu-cve-tracker:master
Proposed by
Paulo Flabiano Smorigo
Status: | Merged |
---|---|
Merged at revision: | a4f35692b4ff2a9d65758b18b4e16a53aae4d134 |
Proposed branch: | ~pfsmorigo/ubuntu-cve-tracker:pfsmorigo/pocket_field_for_publish_cves |
Merge into: | ubuntu-cve-tracker:master |
Diff against target: |
149 lines (+30/-3) 7 files modified
scripts/publish-cves-to-website-api.py (+11/-2) test/website_api/use_esm_status_for_eol_releases.json (+2/-0) test/website_api/use_esm_status_if_esm_release (+2/-0) test/website_api/use_esm_status_if_esm_release.json (+8/-1) test/website_api/use_public_status_for_no_eol_releases.json (+2/-0) test/website_api/use_public_status_if_public_release.json (+3/-0) test/website_api/use_ros-esm_status.json (+2/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alex Murray | Approve | ||
Review via email: mp+444872@code.launchpad.net |
Description of the change
This commit adds the pocket field to the payload we send to the web api. More info in:
https:/
Basically checks if it's a product release and use the pocket for it, otherwise will be "security".
The field is already in place and working. I tested with one of our CVEs as you can see here:
https:/
Also, more tests where added in order to test this change.
To post a comment you must log in.
LGTM but I wonder if the code which extracts the pocket from the release needs to be a bit more stricter.