aws / aws/amazon-sagemaker-feedback

Sagemaker Code Editor: Persisting settings and extensions

Open
#75 5 comments 0 reactions 0 assignees View on GitHub
closing-soon code-editor
Dominant language
No language data
Stars
10
Forks
3
PR merge metrics
No merged PRs in 30d

Description

### Product Category

Other

### Question

sagmaker-code-editor uses server, data, and extensions directories located outside of `/home/sagemaker-user`

Thus, any edits to user settings or extensions are not persisted beyond the application's runtime.

Is there any reason why these directories can't be located in the `/home/sagemaker-user` directory mounted via EBS?

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by examining how the SageMaker Code Editor uses the server, data, and extensions directories outside /home/sagemaker-user, and how that directory is mounted via EBS. Confirm whether relocating them would preserve user settings and extensions across application restarts; the issue does not name source files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.