set operator create nested JSON object when a key includes "."

[danielvillalbamota]

Bug description

• Orion version: 3.8.1

When use $set operator in an UPDATE request if the value of an attribute is a JSON object with a key compounds by dots (".") the entity is UPDATED with the JSON object but nested in different subkeys split by the ".".

How to reproduce it
Steps to reproduce the behavior (as an example)

1. Create an entity this way:

curl -iX POST 'http://localhost:1026/v2/entities' \
--header 'Fiware-Service: service' \
--header 'Fiware-ServicePath: /servicepath' \
--header 'X-Auth-Token: ...' \
--header 'Content-Type: application/json' \
--data '{
  "id": "dumps_3.2.0",
  "type": "Vertical"
}'

2. Then update the entity

curl --location 'http://localhost:1026/v2/entities/dumps_3.2.0/attrs' \
--header 'Fiware-Service: service' \
--header 'Fiware-ServicePath: /servicepath' \
--header 'X-Auth-Token: ...' \
--header 'Content-Type: application/json' \
--data '{
  "upgrades": {
    "type": "Json",
    "value": {
      "$set": {
        "dumps_3.1.0": {
          "folder": "dumps",
          "version": "3.2.0",
          "path": "upgrades/3.1.0-to-3.2.0"
        }
      }
    }
  }
}'

3. The entity loaded in the CB

{
    "id": "dumps_3.2.0",
    "type": "Vertical",
    "upgrades": {
        "type": "Json",
        "value": {
            "dumps_3": {
                "1": {
                    "0": {
                        "folder": "dumps",
                        "version": "3.2.0",
                        "path": "upgrades/3.1.0-to-3.2.0"
                    }
                }
            }
        },
        "metadata": {}
    }
}

Expected behavior
The entity is expected within the format which was sent.

[fgalan]

Fixed by PR #4324