Allow disabling launcher in RStudio Workbench
Open
Nobody has claimed this yet.
team: workbench
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
There are cases where we (or customers) want to use RSW without launcher.
We should test this case and ensure that launcher.enabled = false is functional. Right now:
- the launcher startup does not fire, so RBAC is not passed through
- launcher still tries to start (because it is baked into the container)
- the container struggles and does not fire as a result
- you can fix manually (I presume) by blocking the
/startup/launcherdirectory with anemptyDir
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 by tracing how launcher.enabled is handled in the Helm resources and how the /startup/launcher path is started inside the container. Deploy or test with launcher.enabled = false and verify that launcher does not start, RBAC still passes through, and the container becomes ready without manually masking the path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100