Arvados

Draft text for a --filters option, since I just implemented it in #21452 and it's fresh in my head:

--filters: Add arbitrary filters to limit which Arvados objects are accessible from this mount. Write filters in JSON format, using the same qualified field syntax as the groups/contents API method [link]. You can provide the filter list either as a single JSON string on the command line, or as a path to a file with JSON to read.

Note that filters may not be consistently applied to objects you create via the mount.

Example value: Exclude all intermediate workflow outputs, log collections, and filter groups from this mount.

--filters='[["collections.properties.type", "not in", ["intermediate", "log"]], ["groups.class", "!=", "filter"]]'

Example value: Read and apply filters from the file at /etc/arvados/mount-filters.json.

--filters=/etc/arvados/mount-filters.json

21504-arv-mount-reference @ e0724a24547a1e22377a4ec2fa077b7c3597dbfd - developer-run-tests: #4057

As a practical matter, I was always going to start writing the documentation by copying and pasting the output from arv-mount --help. So, I started by improving that output, making it more organized and consistent.

This branch adds a dedicated FUSE section to the SDK section. I think we should aim towards making the "SDK" section more of a "User Reference" section. It could cover both language SDKs and command line tools. We already do some of this. Note that we already had a page about installing arv-mount here, so this is just expanding that. More thorough reorganization can happen as part of/after #16055.

• All agreed upon points are implemented / addressed.
  • Yes
• Anything not implemented (discovered or discussed during work) has a follow-up story.
  • N/A
• Code is tested and passing, both automated and manual, what manual testing was done is described
  • See above
• Documentation has been updated.
  • That's all this branch does
• Behaves appropriately at the intended scale (describe intended scale).
  • No change in scale
• Considered backwards and forwards compatibility issues between client and server.
  • No change in compatibility
• Follows our coding standards and GUI style guidelines.
  • Yes

The documentation updates look very nice, thanks!

I've found a bug in doc/Rakefile, it wasn't possible to just run rake or rake -T to list the available options. This fixed it:

diff --git a/doc/Rakefile b/doc/Rakefile
index 3ec494f57d..f2932284d9 100644
--- a/doc/Rakefile
+++ b/doc/Rakefile
@@ -80,7 +80,7 @@ $build_sdks = begin
       if sdk.can_build?
         sdk
       else
-        puts "Warning: cannot build #{name.replace(/SDK$/, ' SDK')} documentation, skipping".colorize(:light_red)
+        puts "Warning: cannot build #{name.gsub(/SDK$/, ' SDK')} documentation, skipping".colorize(:light_red)
       end
     end
   else