Track software update discoveries #2540
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nelsonkopliku
force-pushed
the
improve-suma-consistency
branch
4 times, most recently
from
ca418b6
to
b0a8ea0
Compare
nelsonkopliku
changed the title
nelsonkopliku
force-pushed
the
improve-suma-consistency
branch
3 times, most recently
from
3eda5a2
to
c2b6202
Compare
nelsonkopliku
added
enhancement
nelsonkopliku
force-pushed
the
improve-suma-consistency
branch
from
c2b6202
to
7f173d4
Compare
nelsonkopliku
force-pushed
the
improve-suma-consistency
branch
from
7f173d4
to
cd5f2d3
Compare
dottorblaster
approved these changes
Apr 29, 2024
nelsonkopliku
force-pushed
the
improve-suma-consistency
branch
from
cd5f2d3
to
afa71d3
Compare
…es discovery results
nelsonkopliku
force-pushed
the
improve-suma-consistency
branch
from
afa71d3
to
7faed99
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces tracking of software updates discovery results.
relevant_patchesandupgradable_packagesof a host are trackedfailure reasonis tracked (issues when authenticating/system id retrieval/relevant patches retrieval/upgradable packages retrieval)Note that there can be at most one tracked discovery per host, that gets replaced by newer discoveries.
What's next: the tracked discoveries can be queried in
/hosts/:host_id/software_updatesand possibly later also on overviews.How was this tested?
Automated tests and manually.