Description of problem:
Ability to add a custom attribute (to provider) that already exists
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. (via API) add custom attributes with name <name>
2. (via API) add custom attributes with name <name>
The custom attribute has successfully added (overrided the existent one)
You should see an error, i.e. "Custom attribute <name> already exists"
I did not found "custom" attributes here:
Are we talking of custom attributes for VMs? (or Instances ,etc, depending on the provider)
I already used "custom attributes" to VMs/Instances, but i did not find other "custom attributes".
In case of custom attributes for VMs/Instances, that behavior (while incorrect) is quite convenient.
Gilad Please add:
The request you are using (POST, PUT etc)
the entire body
url: https://<appliance IP>/api/providers/1/custom_attributes
There seems to be an intent in the code to allow "edit" from "add":
This code is common for Vms and Providers,
and as Guillermo stated in comment 2 this could be quite convenient.
However, this seems to be a confusing behaviour.
Tim, what do you think?
As per conversation in Gitter, this is intended behavior: