> + @Path("/users")
> + @RequestFilters(AuthenticateRequest.class)
> + @Fallback(NullOnNotFoundOr404.class)
> + ListenableFuture<? extends User> add(@PayloadParam("username") String
> userName,
> + @PayloadParam("email") String
> userEmail,
> + @PayloadParam("enabled") boolean
> enabled,
> + @PayloadParam("OS-KSADM:password")
> String password);
> +
> + /**
> + * @see UserApi#delete(String)
> + */
> + @Named("user:delete")
> + @DELETE
> + @Path("/users/{userId}")
> + @RequestFilters(AuthenticateRequest.class)
> + @Fallback(TrueOnNotFoundOr404.class)
Is this desirable behaviour? Are all user applications necessarily not going to
care whether the user we try to delete actually existed or not?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/290/files#r9715343
