You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've recently looked into using our ERRDAP instance with a Minio S3 object store. Unfortunately it looks like ERDDAP currently only works with AWS S3 locations. Is this something that could be added in? It certainly would be a big help for us and hopefully could be useful for others
The text was updated successfully, but these errors were encountered:
When I wrote the S3 support, it only existed at Amazon. I didn't anticipate that would change, but I suspect there is a straightforward way to deal with this.
Currently, if ERDDAP sees that a file's path matches String2.AWS_S3_REGEX (which is Amazon-specific), it knows to deal with the file via the AWS S3 Java API. Since files in your S3 installation don't match that regex, ERDDAP just sees them as goofy/invalid file names. Perhaps there could be a new tag (in datasets.xml?) to specify additional regexes for other S3 installations. I'll leave it to Chris to consider this.
Hello,
We've recently looked into using our ERRDAP instance with a Minio S3 object store. Unfortunately it looks like ERDDAP currently only works with AWS S3 locations. Is this something that could be added in? It certainly would be a big help for us and hopefully could be useful for others
The text was updated successfully, but these errors were encountered: