Join GitHub today
Add extension point for user preferences #3383
This pull request will implement an optional extension point to extend the user-preferences in a dynamic, admin-controlled way.
The admin defines in a yaml files allowed settings (name, type ...). A user can enter these settings and it will be saved in the user-object as external user preferences. These settings will become available inside the User object and with this accessible everywhere else.
Password Parameter Implementation (#3121)
A tool needs a password or any user-specific information, like @erasche Apollo stuff. Such a tool just need to assume the variable that it needs as environment variable ($MY_APOLLO_SERVER). An admin uses the
Webhooks can use personalized data
We have a overlay-search in development and it would be great if plugins can collect user-preferences, like the
Bjoern's Blue Sky Idea
I would like to run a pulsar VM in our OpenStack cloud and register this specific VM in my account so that a few of my jobs can be calculated in my personal VM ... enabling me to bring my own compute resources.
I promise to write some documentation about the connection to
If you haven't touched any JS directly (guessing from the files included in this PR), there should be no changes to the
@mvdbeek I think what you are seeing there is our first version, adding a complete new category to the user-preference menu. Later one we just decided to extend the already existing one to not clutter the main menu, if I recall correctly. Looking back before the rebase: https://github.com/galaxyproject/galaxy/compare/dev...bgruening:5a86e3c5ca09932a67957afe44d9444dff8474f0?expand=1 are also no changes to client.
I think the changed static content is due to different node versions that build slightly different artifacts. I will try to get rid of those.