Admin UI or user defined pluggable Galaxy file sources

[bgruening]

The Infrastructure for writing to pluggable Galaxy file sources exists now for a few releases. Thanks @jmchilton!

Mike has a use-case related to the ANIVL project, where it would be nice if an Admin or a user could add pluggable Galaxy file source plugins.

In an admin UI, I can imagine that Galaxy is writing to the https://github.com/galaxyproject/galaxy/blob/dev/lib/galaxy/config/sample/file_sources_conf.yml.sample file. For a user-based implementation, we probably need to store is in the user session.

xref: #10152
#9888

[bgruening]

We could tackle this in 3 steps.

1. Add a schema to all the file plugins. So that we can validate the settings of one plugin, e.g. is bucket_name required etc. Optionally, validate the file_sources_conf.yml during startup. (if that does not already exist)
2. create a new section in the user-preference page called "add new remote files" and add a wizard that guides you through the process of setting up a files-plugin based on the schema from step 1)
3. whenever we load the files plugin, load it from the static admin-configured file_sources_conf.yml file and the user-configured ones.

I hope that makes sense.

[hujambo-dunia]

Just a note that @davelopez mentioned that @jmchilton would be taking this ticket instead.

[davelopez]

Yep, thanks for taking this one @jmchilton!