RSW: chart support for `vscode.extensions.conf`
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
The admin guide explains that one can specify additional vscode extensions which will be installed during session start in this file.
I hoped this config file could be populated already via the helm chart (e.g. via config.session.vscode.extensions.conf) using verbatim notation.
This does not seem yet supported, hence I made the required changes in the session image at /etc/rstudio/vscode.extensions.conf which works as the helper script /usr/lib/rstudio-server/extras/scripts/install-vs-code-ext.sh looks at this place.
I'd like to say thanks for this simplification - so far I installed a bunch of extensions in a shared extensions dir. This option makes things a lot easier and more flexible!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the admin guide section on vscode.extensions.conf and inspect how the chart handles session configuration, using config.session.vscode.extensions.conf as the requested entry point. Check the interaction with /etc/rstudio/vscode.extensions.conf and /usr/lib/rstudio-server/extras/scripts/install-vs-code-ext.sh; done means the chart can populate the file with verbatim extension configuration during session startup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100