[EnMasse] Upcoming REST API changes

[Gordon Sim]

On 08/05/18 10:50, Rob Godfrey wrote:
> 
> 
> On 8 May 2018 at 11:43, Gordon Sim <gsim at redhat.com 
> <mailto:gsim at redhat.com>> wrote:
>     By instinct I
>     actually prefer a model that only operates on the address-space as a
>     whole rather than focusing on individual addresses.
> 
> 
> I can see the validity in both - but for creating an address space I 
> think it should be possible to post a single "document" which includes 
> the address space definition and within it all the addresses.  (Always 
> having to send the entire document is painful when you have 10,000 
> addresses and you only want to update one... and makes it easier to 
> accidentally delete addresses accidentally due to races between updates).

I suspect address-spaces of that size will often be defined in some 
version controlled file. I accept that there may be cases where more 
granular forms are convenient.

> The address space is an entity which is also a container for other 
> entities (addresses) you should be able to mutate this either by 
> resending the entire document, or by modifying parts of the document 
> using a hierarchical path selector of some kind (i.e. a URL which talks 
> to a subsection of the larger document).

I don't disagree!