Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

put should upload to the directory specified in regexp #19

Closed
vito opened this issue Dec 14, 2015 · 2 comments
Closed

put should upload to the directory specified in regexp #19

vito opened this issue Dec 14, 2015 · 2 comments

Comments

@vito
Copy link
Member

vito commented Dec 14, 2015

Today you have to specify regexp: path/to/foo-(.*).tgz, which is fine and all for checking, but gets awkward when you want to upload a file to path/to. The only way to do that currently us via using from and to, which is deprecated and a bit confusing in how it works.

Instead, the file specified should be uploaded to whatever parent directory is specified in the regexp.

Full usage example:

resources:
- name: foo
  type: s3
  source:
    bucket: my-bucket
    regexp: path/to/foo-(.*).tgz

jobs:
- name: upload-foo
  plan:
  - task: make-foo
    # ...
  - put: foo
    params: {file: made-foo/foo-*.tgz}
@concourse-bot
Copy link
Collaborator

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:

  • #110040642 put should upload to the directory specified in regexp

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

@concourse-bot
Copy link
Collaborator

Hello again!

All stories related to this issue have been accepted, so I'm going to automatically close this issue.

At the time of writing, the following stories have been accepted:

  • #110040642 put should upload to the directory specified in regexp

If you feel there is still more to be done, or if you have any questions, leave a comment and we'll reopen if necessary!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants