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

Specifying working directory for aws sync command? #13

Open
phillbaker opened this issue Feb 20, 2017 · 5 comments
Open

Specifying working directory for aws sync command? #13

phillbaker opened this issue Feb 20, 2017 · 5 comments

Comments

@phillbaker
Copy link

phillbaker commented Feb 20, 2017

Since concourse puts are passed in the directory containing all of a plan's outputs, is it currently possible to sync only one output directory to the root of a s3 bucket?

It looks like we'd have to pass an additional parameter to either cd into or use in the aws sync line. Would you be open to that as a pull request?

Looks like someone tried something similar here: pivotal-sydney@3888817

@gaelL
Copy link

gaelL commented Jun 8, 2017

It would be great to have this feature. I'm using this resource and having the same need.

@mcblair
Copy link
Contributor

mcblair commented Jul 2, 2017

@phillbaker Are you able to use pivotal-sydney's s3-resource-simple?

@phillbaker
Copy link
Author

@mcblair my memory is a bit hazy, but I believe I did try to use their fork, and something didn't line up. We ended up forking and added the changes in #14.

@mcblair
Copy link
Contributor

mcblair commented Jul 3, 2017

@phillbaker Same thing with me - their fork/docker image on docker hub wasn't savvy. Forked it and added the changes myself.

@gaelL
Copy link

gaelL commented Feb 20, 2018

This issue seems to be opened since 1y, and have several PR to fix it : like #14 and #21 and some people are forking specially because of this need (pivotal-sydney@3888817)

@afeld Is there anything we could do to help to fix that issue ?

Regards,

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

3 participants