Feature Request: Collect software path and binaries information in extmodules workflow

[ericblau]

The OnDemand folks want to be able to allow users to run GUI executables from ACCESS-CI resources from the OnDemand portal. To do this, they need the actual executable and path information.

It appears that, at least for lmod, the path information is easily obtained from the lmod cache, and slightly less easily parsed from the lua module files.

I have yet to investigate how easily obtainable this info is from sites running modules (or Valet, or anything else).

Getting the binaries list will require filesystem operations to find all executable files at that path.

Open questions include:

• Whether to try to scope this to only GUI packages, and, if so, how
• Whether this information should be gathered for all packages
• Whether this information should be scraped on every run of the workflow
• Whether this should be in the extmodules workflow, as it could possibly be a separate workflow
• Schema for storing this info (I think it will have to be in Extensions, as I'm pretty sure Glue2 doesn't include binaries or binary paths in its schema)

[ericblau]

JP suggested that we could look as storing this info as a handle_type.