The exploring of remote and local datasets now happens entirely in the datastore module. The wk side only forwards the request (after storing the credentials in postgres and then sending only the credential IDs).

This means that the user can select which datastore should handle the exploring.

It also means that for local datasets, the directory whitelist config setting does not have to work on the wk server side, only on the datastore side. Thus, this feature is now also available for multi-datastore setups where the wk side does not have access to the same file systems.

TODO

• Frontend: Allow selecting datastore, pass its name to /datasets/exploreRemote parameters (needs to be equal for all items in the list)

Steps to test:

• Explore remote dataset, should work
• Explore local dataset with file://, should yield error message suggesting you add the directory to the config setting
• after doing that it should work
• If you want to be really diligent: test this with a datastore on a different file system (but I’d say it’s ok to see if this works in production)

Issues:

• fixes localFolderWhitelist for dataset exploring should work for multi-datastore setup #7781

• Updated changelog
• Removed dev-only changes like prints and application.conf edits
• Considered common edge cases
• Needs datastore update after deployment