Currently many keywords ran during robot init are defined to `PUT` specific resource into AAI with relevant relationships. This approach makes it hard to reuse already created entities by binding them to other resources as no relevant keywords are prepared.

Example issue can be found when one would like to use already created customer to bind with new services. In this scenario Customer won't be updated with new services relationship, as operation fails on `PUT` operation used improperly (part of `Load Customer`>`Create Customer For VNF Demo`>`Run Put Request`):

Received response from [aai]: {"requestError":{"serviceException":{"messageId":"SVC3000","text":"Invalid input performing %1 on %2 (msg=%3) (ec=%4)","variables":["PUT","business/customers/customer/CNF_Demonstration","Precondition Required:resource-version not passed for update of /business/customers/customer/CNF_Demonstration","ERR.5.4.6130"]}}}

Similar behavior can be found during creating tenants (Tenant + Cloud region pair is always created, no option to bind existing cloud with a new tenant) and complexes (complex is added bound to certain cloud-region, no keyword to bind existing complex to existing cloud-region).

Adding such behavior would ease sharing as much of "same" dummy entities between VNF and CNF clouds/services as possible.