Project

General

Profile

Actions

Bug #10216

closed

"id" setting is silently ignored for new group created through the REST API.

Added by Dmitry Svyatogorov about 7 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
API
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
100
Name check:
Fix check:
Checked
Regression:

Description

According to https://www.rudder-project.org/rudder-api-doc/#api-Groups-createGroup
new group can be created with the exact "id". But as for Rudder 4.0.2, "id" setting is silently ignored and new UUID is generated.
For example try to PUT the following json:
{
  "id": "9a92538b-d01f-4157-9fff-ed1d1a8d3443",
  "category": "GroupRoot",
  "enabled": true,
  "displayName": "###TEST#",
  "query": {
    "select": "node",
    "composition": "And",
    "where": [
      {
        "objectType": "node",
        "attribute": "nodeHostname",
        "comparator": "regex",
        "value": ".*\\.xxx\\.tld" 
      }
    ]
  }
}
  • The answer looks like
    {"action": "createGroup","id": "2ef61fa0-426d-40a1-99c1-c1f62b4d5664","result": "success"…
    

    Then check the "id" in answer body / WEB-UI against the requested value.

This seriously complicates group & rule transmitting between 2 nodes through REST-API because of need in translation dictionary.

Actions

Also available in: Atom PDF