Project

General

Profile

Actions

User story #17367

closed

Missing info about if a node is a relay in API and capabilities need to to in management technologie

Added by François ARMAND about 4 years ago. Updated about 4 years ago.

Status:
Released
Priority:
N/A
Category:
API
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
To do
Fix check:
Checked
Regression:

Description

When we query information about a node for managementTechnologyDetails, we don't have the information about the fact that the node is a policy serveur (root or relay) or a simple node.
This is blocking some integration scripts for users.

Ex of content for root:

       "managementTechnologyDetails": {
           "cfengineKeys": [
            "-----BEGIN CERTIFICATE--...----END CERTIFICATE-----" 
          ],
          "cfengineUser": "root",
          "capabilities": [
            "acl",
            "cfengine",
            "curl",
            "http_reporting",
            "jq",
            "xml",
            "yaml" 
          ],
          "serverRoles": [
            "rudder-db",
            "rudder-reports",
            "rudder-server-root",
            "rudder-webapp" 
          ]
        }
      }

=> add "role" = { root, relay, node } so that it matches (ie same logic to decide) what is displayed in node details.

Actions #1

Updated by François ARMAND about 4 years ago

  • Status changed from New to In progress
Actions #2

Updated by François ARMAND about 4 years ago

  • Tracker changed from Bug to User story
  • Subject changed from Missing info about if a node is a relay in API to Missing info about if a node is a relay in API and capabilities need to to in management technologie
  • Target version changed from 5.0.18 to 6.1.0~beta3
  • Priority deleted (0)

Actually, capabilities and serverRoles were added in rudder 6.1. But we want to have them in managementTechnology, and we want to normalize names.

Make it happen in 6.1, we will see if a backport is needed.

Actions #3

Updated by François ARMAND about 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Alexis Mousset
  • Pull Request set to https://github.com/Normation/rudder/pull/2963
Actions #4

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.1.0~beta3 to 6.1.0~rc1
Actions #5

Updated by François ARMAND about 4 years ago

  • Status changed from Pending technical review to Pending release
Actions #6

Updated by Nicolas CHARLES about 4 years ago

  • Fix check changed from To do to Checked
Actions #7

Updated by Vincent MEMBRÉ about 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.0~rc1 which was released today.

Actions

Also available in: Atom PDF