Naming of "private" flag is confusing (low-priority, docs) about s3-resource HOT 4 CLOSED

Related to the findings in concourse/concourse#622 - URL signing should probably be done with put instead, which will be a good opportunity to pick a better name. (private should remain supported for backwards-compatibility).

Opened #53 to express this.

from s3-resource.

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

• #129578905 Naming of "private" flag is confusing (low-priority, docs)

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

from s3-resource.

Also, the default validity of the signed AWS URL is 24 hours and is hardcoded deep in the s3 resource. If we could have this parametrized that would be great!

from s3-resource.

Indeed, I would recommend that people tend to the Validity window for a longer-than-expected time, for the following reason

There may be an undesirable behavior where Baggage Claim can't assure that the signed S3 URL that it serves up is valid any more. See concourse/concourse#622 for one proposed feature that would maybe help alleviate it. But otherwise, it's going to get hairy.

Concourse is great at properly versioned items; for S3, the url file that comes along for the ride is fine, but outside the umbrella of versioning. So there's no way to handle it in the Concourse idiom.

Getting a signed URL is a nice bonus, but not within the expected scope for what a resource can guarantee.

from s3-resource.