Skip to content

Switching a S3 resource's file from unversioned to versioned causes it to fail with "Specified version doesn't exist" #113

@xtreme-sameer-vohra

Description

@xtreme-sameer-vohra

Reproduction Steps

  1. Create a unversioned S3 bucket and add a file ( foo.txt )
  2. Create a pipeline that uses a s3 resource pointing to foo.txt
  3. Switch the S3 bucket to versioned and upload another file ( bar.txt )
  4. Modify the existing s3 resource pointing it to bar.txt
  5. At this point foo.txt has no version id and bar.txt does

Actual

Running the pipeline fails with the following error:
screen shot 2015-08-06 at 11 23 59 am

Expected

Running the pipeline should not fail. Pushing the same configuration to a brand new pipeline works.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions