> @@ -149,7 +165,18 @@ public void write(BlobStore blobStore, String bucket,
> String blobName, Blob blob
> }
> }
>
> - blobStore.putBlob(bucket, blob, options);
> + if (signedRequest) {
> + BlobStoreContext context = blobStore.getContext();
> + HttpRequest request = context.getSigner().signPutBlob(bucket, blob);
> + HttpClient httpClient = context.utils().http();
> + HttpResponse response = httpClient.invoke(request);
> + int statusCode = response.getStatusCode();
> + if (statusCode != 200 && statusCode != 201) {
> + throw new IOException(response.getStatusLine());
> + }
Curious why we're having to essentially circumvent the "normal" `blobStore.put`
logic and do our own request management here. Would it make more sense to add
`putSignedBlob` and `getSignedBlob` to BlobStore itself? Then this would also
be available outside karaf..?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/20/files#r5300628
