Skip to content

Misconfiguring a S3 resource doesn't throw an error and job stays in pending state #114

@xtreme-sameer-vohra

Description

@xtreme-sameer-vohra

Reproduction Steps

  1. Create a pipeline that uses a s3 resource pointing to a file that doesn't exist
  2. Push the pipeline for the first time

Actual

Job hangs in pending state and doesn't throw an error, while the resource has "Checking Successfully" green.

Expected

Start the job and throw and error saying fetching resource failed.

Note

Once a S3 resource has been fetched successfully, then changing the file value to a non-existent field yields the desired error. So the error only happens if the resource has never fetched successfully.

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