osbuild: add openscap profile and compliance policy id to facts #903
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
achilleas-k
requested changes
Sep 4, 2024
croissanne
force-pushed
the
security-facts
branch
from
d317e3b
to
dafb40d
Compare
kingsleyzissou
approved these changes
Sep 4, 2024
achilleas-k
approved these changes
Sep 4, 2024
|
Need to get #904 merged to unblock. |
Allows registered systems to be coupled to existing compliance policies.
kingsleyzissou
force-pushed
the
security-facts
branch
from
dafb40d
to
14f94f5
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.
Allows registered systems to be coupled to existing compliance policies.
As it stands this would require composer to fill in these facts in the image options as it does for the api types. For the openscap profile id we could fill it in automatically if an openscap customisation is defined, open to opinions.