Skip to content

AJDA-2169 - Switch autosave to data-loader internal endpoint #32

Merged
ErikZigo merged 8 commits into
masterfrom
erik-AJDA-2169-autosave
Feb 17, 2026
Merged

AJDA-2169 - Switch autosave to data-loader internal endpoint #32
ErikZigo merged 8 commits into
masterfrom
erik-AJDA-2169-autosave

Conversation

@ErikZigo

@ErikZigo ErikZigo commented Feb 9, 2026

Copy link
Copy Markdown
Contributor

Release Notes

  • Prepares notebook autosave to work without a Storage API token, as part of the broader effort to remove tokens from Jupyter sandbox containers
  • Switches the autosave script to use the data-loader's internal save path, restricted to localhost only
  • This release has no user-facing effect on its own — it only takes effect once new JupyterLab images are built with this package and distributed via runtimes
  • Aligns minimum Python version (3.10) with what's actually running in Keboola Jupyter container images

Change Type

Minor

Impact Analysis

  • Who's affected: Jupyter-type sandbox users and the autosave background process
  • Main value: Removes the need to expose a Storage API token inside notebook containers
  • Risks: Low — requires data-loader 4.3 (deployed via sandboxes#575) to already be in place; the internal save endpoint must be available before new JupyterLab images are distributed

Customer Communication Plans

No external communication needed. The user experience is identical — notebooks continue to autosave transparently.

Justification

Jupyter sandbox containers currently require a Storage API token for notebook autosave, which is a security concern. This change is step 2 of a multi-phase effort to remove storage tokens from sandbox containers entirely, as part of the Sandbox API deprecation initiative.

Deployment Plan

  • Merge and release notebook-utils 2.3.0
  • Build new JupyterLab sandbox images for Python 3.10 containing the updated notebook-utils
  • Register the new images in Sandboxes runtimes

Rollback Plan

Since this release has no effect on its own, no rollback is needed at this stage. If issues arise after step 3 (new JupyterLab images), rebuild the images with the previous notebook-utils version 2.2.0 to restore the original token-based autosave path. No data loss or service disruption expected.

Post-Release Support Plan

  • Watch for unexpected errors on the internal save path
  • Confirm autosave continues to work correctly across all sandbox environments

@linear

linear Bot commented Feb 9, 2026

Copy link
Copy Markdown

@ErikZigo ErikZigo force-pushed the erik-AJDA-2169-autosave branch 3 times, most recently from 07c9f83 to 2286e66 Compare February 10, 2026 14:38
@ErikZigo ErikZigo force-pushed the erik-AJDA-2169-autosave branch from d352e4c to e427138 Compare February 15, 2026 15:01
@ErikZigo ErikZigo force-pushed the erik-AJDA-2169-autosave branch from e427138 to 2c9a449 Compare February 15, 2026 15:07
@ErikZigo ErikZigo marked this pull request as ready for review February 15, 2026 16:38
Comment thread .github/workflows/test.yml
Comment thread setup.py Outdated
@ErikZigo ErikZigo changed the title Erik ajda 2169 autosave AJDA-2169 - Switch autosave to data-loader internal endpoint Feb 15, 2026
@ErikZigo ErikZigo requested a review from odinuv February 16, 2026 17:08
@ErikZigo ErikZigo merged commit f16fc60 into master Feb 17, 2026
1 check passed
@ErikZigo ErikZigo deleted the erik-AJDA-2169-autosave branch February 17, 2026 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants