'Section' is not honored when custom attributes added through the api. Section is always set to default "Metadata", This causes problem later when removing the custom attributes through the api. backport request for : https://github.com/ManageIQ/manageiq/pull/12913
Please provide steps to reproduce.
Gilad, Add a Custom Attribute with a section different than "metadata" before it used to ignore the section that you tried to set.
________________________________ { "action": "add", "section": "somesection", "resources": [{ "name": "foo", "value": "17" }]} _____________Results:________________ { "results": [ { "id": 2363, "section": "metadata", "name": "foo", "value": "17", "resource_type": "ExtManagementSystem", "resource_id": 1, "source": "EVM", "serialized_value": "17" } ] }
It is a very old bug, The system has changed since then to only allow specific sections. Please try with "cluster_settings" https://github.com/ManageIQ/manageiq/pull/13360
{ "action": "add", "section": "cluster-settings", "resources": [{ "name": "foo1", "value": "171" }]} __________________Results:__________________ { "results": [ { "id": 2364, "section": "metadata", "name": "foo1", "value": "171", "resource_type": "ExtManagementSystem", "resource_id": 1, "source": "EVM", "serialized_value": "171" } ] }
Note: not working with "cluster_settings" as well.
The problem was a bad API call (the section field was out) --> moving to VERIFIED