Skip to content

[FSTORE-2086] Add support for disabling Uploads to Hopsworks - #632

Draft
manu-sj wants to merge 1 commit into
logicalclocks:mainfrom
manu-sj:FSTORE-2086
Draft

[FSTORE-2086] Add support for disabling Uploads to Hopsworks#632
manu-sj wants to merge 1 commit into
logicalclocks:mainfrom
manu-sj:FSTORE-2086

Conversation

@manu-sj

@manu-sj manu-sj commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Part of FSTORE-2086. Backend PR: logicalclocks/hopsworks-ee#3224

What

Documents the new upload_policy cluster configuration on the Cluster Configuration page: the three values (enabled, admins_only, disabled), that the backend enforces the policy so it covers the Python API as well as the UI, and that a refused upload returns HTTP 403 while the UI disables the controls instead.

Why these particular points are called out

  • The two ways of setting it interact. A value set in the Helm chart is reapplied on every upgrade, so a change made from the Configuration page holds only until the cluster is next upgraded. Someone who sets this from the UI and expects it to persist would otherwise be surprised by an upgrade quietly restoring the chart value.
  • The name overpromises. "Uploads disabled" reads as stronger than it is, so the page states the limits: the policy governs uploading new files only, it does not stop a python library being installed from a requirements file already in a project, and it does not remove files uploaded before the value changed.
  • Unrecognised values fall back to enabled. Documented so an operator who mistypes the value does not assume uploads are blocked when they are not.

Placement

Added as a section on setup_installation/admin/variables.md rather than a new page. That page is the Cluster Configuration reference, and no page in the repo documents individual variables, so there was no per-variable reference to extend. No mkdocs.yml nav change is needed for a section on an existing page.

Follows the repo conventions: one sentence per line, and no restriction stated without its reason.

Testing

npx markdownlint-cli2 docs/setup_installation/admin/variables.md — 0 errors.

The full mkdocs build -s was not run; it needs the uv environment plus the hopsworks-api install for the API docs section, and this change adds no new page, link, or nav entry that a build would newly validate.

Ticket: https://hopsworks.atlassian.net/browse/FSTORE-2086

https://hopsworks.atlassian.net/browse/FSTORE-2086

Documents the upload_policy configuration on the Cluster Configuration
page: the three values, that the backend enforces the policy so it
covers the Python API as well as the UI, and that the two ways of
setting it interact, since a value from the Helm chart is reapplied on
every upgrade and overrides a change made from the Configuration page.

States the limits explicitly, because "uploads disabled" reads as
stronger than it is. The policy governs uploading new files only, so it
does not stop a library being installed from a requirements file already
in a project, and it does not remove files uploaded earlier.

No nav entry is needed; the section is added to an existing page.

Signed-off-by: Manu Sathyarajan Joseph <manu.joseph@logicalclocks.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.

1 participant