Using v1.2.10 causes already working `put` step to fail

[anijayn]

Since the new changes to this resource, the put step fails with the following error in our pipeline job.

+ dirname /opt/resource/out
+ source /opt/resource/emit.sh
/opt/resource/out: 49: /opt/resource/out: source: not found

Notes

• We use this resource to upload our static assets to an S3 bucket and it was working fine with v1.2.6.

[bk1216]

I’m also facing the same issue in get step

[bk1216]

@anijayn is it possible to use specific tag when fetching an image ? Please let me know

Thanks

[anijayn]

@bk1216 Yes, you can. I just updated my current pipeline's resource config to this:

  - name: simple-s3
    type: registry-image
    source:
      repository: 18fgsa/s3-resource-simple
      tag: 1.2.6

v1.2.6 was the last working version in our pipeline

[bk1216]

@anijayn Thank you
Not seeing the above issue with v1.2.12

[charles-dyfis-net]

source is a bashism; . is the POSIX sh equivalent. This was thus fixed in c493d03