> +@Consumes(MediaType.APPLICATION_JSON)
> +@Produces(MediaType.APPLICATION_JSON)
> +@RequestFilters({ ServiceKeyAuthentication.class })
> +@Path("/api/servicekeys")
> +public interface ServiceKeysApi {
> +
> + @Named("servicekeys:list")
> + @GET
> + List<ServiceKey> listServiceKeys();
> +
> + @Named("servicekeys:create")
> + @POST
> + ServiceKey createServiceKey(@WrapWith("description") String description);
> +
> + @Named("servicekeys:delete")
> + @Fallback(VoidOnServiceKeyNotFoundAnd500.class)
WRT the comment in the other fallback, this is a write operation, but we use
these fallbacks, because the delete operations are often used to release
resources, and having to try/catch there is not convenient.
However, to follow the pattern used in other jclouds providers I'd change this
method to return a `boolean` and change the fallback to return `false` if there
is an exception. jclouds will return `true` by default if the response succeeds.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/149/files#r26263224
