[EnMasse] Upcoming REST API changes

[Gordon Sim]

On 08/05/18 10:20, Rob Godfrey wrote:
> 
> 
> On 8 May 2018 at 11:02, Gordon Sim <gsim at redhat.com 
> <mailto:gsim at redhat.com>> wrote:
> 
>     On 08/05/18 04:17, Ulf Lilleengen wrote:
> 
>         For addresses, the REST API also changes in the same way, making
>         the addresses scoped by both namespace and address space. The
>         metadata.addressSpace field will be mandatory now that it cannot
>         be inferred from the URL path anymore.
> 
>         Creating multiple addresses at once using AddressList is
>         removed, as this is handled client-side when using the kubectl
>         command line and not server-side. We could still keep it at
>         server side if we think it will be of value.
> 
> 
>     To create 10,000 addresses, I think one request with a large payload
>     might be simpler than 10,000 separate requests.
> 
> 
> Agreed - but I think this only makes sense in the context of creating 
> multiple addresses within a single address space.

Indeed. Controlling the set of addresses that make up an address-space 
is in my view the primary function. By instinct I actually prefer a 
model that only operates on the address-space as a whole rather than 
focusing on individual addresses.