Skip to content

unable to meta validate for s3 urls with remote data #149

Description

@quinnwai

Describe the bug
When I supply my own metadata, I am unable to prepend my data with s3:/// in the documentreference content.url . It has to be file:///. Why?

To Reproduce
Steps to reproduce the behavior:

  1. Clone down any data project / remote add a file to a repo
  2. Change the content.url to be prepended with s3:/// instead of file:///
  3. meta validate

Expected behavior
Expected meta validate to pass and file to be downloadable after

Environment (please complete the following information):

  • Version: 0.0.7rc22 (development at 2877cd5)

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions