Update backend configuration for including and excluding buckets #90
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #89.
Update backend configuration to allow users to specify a list of drives to include or exclude from the drives filebrowser upon starting JupyterLab.
The config now contains two new fields,
excluded_drives
andincluded_drives
, through which users can define a smaller set of drives they want to launch JupyterLab with. The given list of drives will be used to populate the UI for the drives manager linked in the above PR. As such, the user will still have control over their full set of buckets and will be able to add drives back to the filebrowser from the excluded list, as well as remove others from the included list.Although both fields are present, only one of them is needed when configuring the drives list - they are just meant to give users a way to easily define the shortest list (e.g.: include only these three drives and exclude all else, opposed to exclude this long list of drives).