stackabletech / stackabletech/issues

Add vscode/git support

Open
#707 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

size/M
Dominant language
No language data
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Description

As I user I want to have access to the vscode plugin/integration within my jupyterhub environment, to be able to version and develop notebooks.

N.B. this covers vscode integration only, and not the other options originally considered (see table below).

Background / Context

From the previous epic (for context):

Demo Tutorial Stage 1 tasks To demonstrate Effort Remarks Priority
Notebook integration with source control directly with terminal S 6
gitsync (required to be in the image) L 11
vscode integration L 7

From the decision:

Stage 2
  • OPA gateway: with distributed spark the Notebook acts as the driver and requests executors Pods from k8s. These Pods in turn can mount all volumes and Secrets in that namespaces. To prevent this from breaking user separation, use OPA gatekeeper to have OPA rules that restrict what the created executor Pods can mount
  • Embedded VSCode Server: provides both notebook-based and IDE-based environments in the same system

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing epic #191 and decision #36, then identify which repository and entry points own the JupyterHub environment; the issue names no files or tests. Define the VS Code-only integration scope and acceptance criteria for accessing VS Code and versioning and developing notebooks before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, vscode
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.