Ability to specify version in the directory path of the regex about s3-resource HOT 7 OPEN

18 months later, what's status on this issue ? We also want to group up all transient artifacts of same version under a unique folder.

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:

• #131332763 Ability to specify version in the directory path of the regex

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

from s3-resource.

I don't really know what to do with this. From what's there I don't see where the ( would come from. Did you have a weird filename or something?

from s3-resource.

No. The filename and path is what is given (output.txt). The version is just semver. When I change the version to be append to the file, it works. But when I try to append version to directory, this error is returned.

from s3-resource.

Ah, yeah that's broken at the moment; the resource expects the final path segment (the filename) to contain the version.

from s3-resource.

same here, a hierarchical/versioned directory structure is quite useful.

dir-VER/

• artefact1
  ...
• artefactN

is preferible in many cases we have than either
dir/

• artefact1-VER
• artefactN-VER

or

dir/

• artefact1/data-VER
• artefact2/data-VER

I read "broken" and not "not implemented", so I guess it was meant to be a current feature until it broke.

from s3-resource.

I'm also screwed by this right now, because I have a CI process that requires the filename be static (homebrew bottles), but I could work around that to create multiple 'versions' by generating them in different root urls.

e.g. instead of just s3://my-bucket/my_static_filename_pattern.tar.gz and thus concourse caching my_static_filename_pattern.tar.gz even though it has changed...

I could put them in s3://my-bucket/my-dynamic-prefix/my_static_filename_pattern.tar.gz and each 'path' would then result in a new version.

Honestly, considering s3 'folders' are actually part of the file name, I think we should be including the prefix in the version anyway.

from s3-resource.