> @@ -325,4 +330,16 @@
> ListenableFuture<ListBlobBlocksResponse>
> getBlockList(@PathParam("container")
> @ParamValidators(ContainerNameValidator.class) String container,
> @PathParam("name")
> String name);
>
> + /**
> + * @see AzureBlobClient#copyBlob
> + */
> + @Named("CopyBlob")
> + @PUT
> + @Path("{toContainer}/{toName}")
> + @OverrideRequestFilters
> + @RequestFilters(value = { AddCopySourceHeader.class,
> SharedKeyLiteAuthentication.class })
Unsure about `AddCopySourceHeader`; this feels like a clumsy way to implement a
compound header. I modeled the interface after the S3 equivalent but perhaps
this is the wrong approach. If I change `fromContainer` and `fromName` to
`fromUrl` I can avoid this entirely and expose the full power of the Azure
interface. Thoughts?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/514/files#r17213002
