sudo rights in openvscode and vre lab

[jelletreep]

Sudo rights can be obtained by adding collaboration members to the src_co_admin group in SRAM

This instruction should probably come in a 'partial' so that it can easily be added to multiple catalog item pages, and maintained on one location

[jelletreep]

Has been added as partial and in OpenVSCode and OpenRefine catalog items!

• Add in VRE lab workspace manual
• Should we add this to Python workbench @dometto ?

[dometto]

I'm also unsure about how we should distribute sudo rights by default. Options are:

1. No sudo rights for anyone. Most secure, least flexible.
2. Sudo for everyone. Most flexible, least secure.
3. Sudo for CO admins only. Some flexibility, some security. This is either the best or the worst of both worlds :)

Personally I think 2 makes the least sense: at least it is good to have the option of designating some but not all users as admin. However, many of the SURF catalog items do use option 2.

Do we want to have separate catalog items with different sudo policies? Or do we want to enforce as much as possible that users try not to use sudo, by having dependencies in their own environments instead of installing them globally, etc---and not give sudo by default?

[jelletreep]

I prefer option 3, in this way users need to make a deliberate choice to give themselves sudo rights. We will add this to the documentation for R and Python workbench now, and I will open an issue in the catalog items repo