Skip to content

Separate use-cases for generating signed object references #106

Closed
@jboynes

Description

@jboynes

There's currently one method for generating signed references:

URL signUrl(BlobInfo blobInfo, long expirationTimeInSeconds, SignUrlOption... options);

There are a number of SignUrlOption types but its not clear from the interface which ones can be used in combination. For example:

  • specifying md5 and contentType should not be allowed for a GET, HEAD or DELETE
  • for PUT, md5 and contentType take their values from BlobInfo but the object hasn't been created yet

I also don't see how extension headers or the base URL would be specified.

Instead, can we use a method chain for this:

  URI get = datastore.signedReference(bucketName, objectName, expiration).toURI();
  String put = datastore.signedReference(bucketName, objectName, expiration)
      .forPut().ofContentType("text/plain").toString();

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.api: storageIssues related to the Cloud Storage API.status: will not fixInvalid (untrue/unsound/erroneous), inconsistent with product, not on roadmap.triage meI really want to be triaged.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions