Conversation
|
So sorry for the slow response on this. Mind updating the README to match? Also, thoughts about using |
|
Sure - can do on both, will take a look tonight. |
|
@phillbaker Thanks, I would be glad to have this feature |
|
@afeld What are your recent thoughts on this? This is a feature that should allow us to get around the warning messages of If you weren't aware already, if you exclude anything with |
Example usage:
```
resources:
- name: <resource name>
type: <resource type name>
source:
access_key_id: {{aws-access-key}}
secret_access_key: {{aws-secret-key}}
bucket: {{aws-bucket}}
jobs:
- name: <job name>
plan:
- task:
config:
platform: linux
image_resource: *node
outputs:
- name: built-project
- put: <resource name>
params:
dir: built-project
```
|
Sorry for the slow turnaround on this, updated the README, and updated the variable name to be |
|
@afeld Any ETA on when this will get merged? |
|
This PR would solve our need to sync a non-working directory. Until this PR is merged, we will have to fork this project. |
|
I could also really use this. Anything blocking the merge? I'd love to help out if something's missing. |
|
Unfortunately you'll need to fork and build yourself. |
|
@mcblair Because you don't expect this to get merged for some reason? Or is this resource not being actively maintained any longer? |
|
I'm not sure what is up with 18F but it's on them. Personally, I forked and have been using my fork since then. |
|
any updates on this? |
|
Any movement on this? |
|
Probably a stupid question 4 years later - but is there any other way to define what get's synced currently without forking? How are people uploading to s3 via concourse nowadays? I've a hard time getting things to upload previous tasks's outputs only. It seems it wants to use only Any help appreciated! |
Example usage:
Closes #13.