Fixes #23930: lost audit/enforce on the node compliance page #5281
Conversation
| } | ||
| in | ||
| req | ||
|
|
There was a problem hiding this comment.
I don't think we want to do that. It will be extremely costly when the number of rules/directives growths, especially since we get all rules/directives, and not the ones for the node.
A better approach would be to extends getNodeComplianceId api to provide the compliance mode - and moreover, I'm pretty sure it's something that would be interesting to have in the public API too.
There was a problem hiding this comment.
The API part is done here : https://github.com/Normation/rudder/pull/5308/files
You can change the decoder at the level of the RuleCompliance and DirectiveCompliance data types : just adding a policyMode field will do, it simplifies also a lot of things in this PR I guess 😄
|
PR rebased |
RaphaelGauthier
force-pushed
the
bug_23930/lost_audit_enforce_on_the_node_compliance_page
branch
from
fdc29d4
to
7ef3328
Compare
|
PR updated with a new commit |
|
PR rebased |
|
I did the change : |
|
Closing this PR, the fix is done in this other one : #5351 |
https://issues.rudder.io/issues/23930