Project

General

Profile

Bug #14241

Missing rule name in compliance API

Added by Nicolas CHARLES 9 months ago. Updated 3 months ago.

Status:
Released
Priority:
N/A
Category:
API
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
74

Description

The name of Directives appears in the output of the compliance API, but not the name of the Rules. This is fairly confusing

#  curl -k -H "X-API-Token:  A3l7RSAqK6AtOtUu3jhw93MbUaQkvsg6" -X GET 'https://localhost/rudder/api/latest/compliance/rules?level=2&prettify=true'
{
  "action": "getRulesCompliance",
  "result": "success",
  "data": {
    "rules": [
      {
        "id": "32377fd7-02fd-43d0-aab7-28460a91347b",
        "compliance": 47.37,
        "mode": "full-compliance",
        "complianceDetails": {
          "successAlreadyOK": 39.47,
          "successNotApplicable": 5.26,
          "unexpectedMissingComponent": 25.0,
          "error": 2.63,
          "unexpectedUnknownComponent": 25.0,
          "successRepaired": 2.63
        },
        "directives": [
          {
            "id": "c16e3a90-b9d7-427d-83c1-d80e33124e4c",
            "name": "File content (from remote template)",
            "compliance": 50.0,
            "complianceDetails": {
              "successAlreadyOK": 41.67,
              "successNotApplicable": 8.33,
              "unexpectedMissingComponent": 25.0,
              "unexpectedUnknownComponent": 25.0
            }
          },

Associated revisions

Revision 39aa684a (diff)
Added by Nicolas CHARLES 5 months ago

Fixes #14241: Missing rule name in compliance API

History

#1

Updated by Alexis MOUSSET 9 months ago

  • Target version changed from 4.3.9 to 4.3.10
#2

Updated by François ARMAND 8 months ago

  • Target version changed from 4.3.10 to 4.3.11
#3

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 4.3.11 to 4.3.12
#4

Updated by François ARMAND 6 months ago

  • Tags set to good first bug
  • Subject changed from Compliance API is inconsistent to Missing rule name in compliance API
  • Target version changed from 4.3.12 to 5.0.10
  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Effort required set to Very Small
  • Priority changed from 0 to 76
#5

Updated by François ARMAND 5 months ago

  • Assignee set to Nicolas CHARLES
#6

Updated by Nicolas CHARLES 5 months ago

  • Status changed from New to In progress
#7

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 5.0.10 to 5.0.11
#8

Updated by Nicolas CHARLES 5 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/2217
#9

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 5.0.11 to 5.0.12
#10

Updated by Rudder Quality Assistant 5 months ago

  • Assignee changed from François ARMAND to Nicolas CHARLES
#11

Updated by Nicolas CHARLES 5 months ago

  • Status changed from Pending technical review to Pending release
#12

Updated by Vincent MEMBRÉ 4 months ago

  • Priority changed from 76 to 75
#14

Updated by Alexis MOUSSET 4 months ago

  • Priority changed from 75 to 74
#16

Updated by Vincent MEMBRÉ 3 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.12 which was released today.

Also available in: Atom PDF