Skip to content

Rework Feature Flags - #401

Open
Bohreromir wants to merge 3 commits into
mainfrom
worktree-chore-372-377-feature-flags-helm
Open

Bohreromir wants to merge 3 commits into
mainfrom
worktree-chore-372-377-feature-flags-helm

Conversation

@Bohreromir

@Bohreromir Bohreromir commented Oct 23, 2026 •

Copy link
Copy Markdown
Member

Description

  • Separates Feature Flags from configuration settings
  • Adds unified validation for both
  • Drops redundant Feature Flags
    • Imho these were redundant like making a difference between PUBLIC_STACKABLE_COCKPIT_STORAGE_RENAME_ENABLED and PUBLIC_STACKABLE_COCKPIT_STORAGE_MOVE_ENABLED happy to be corrected on any decision regarding that

Closes #372, #377

Docs

Release note

Checklist

Author

  • AI review done, findings addressed
  • Tests added or updated
  • Changelog updated (if the repo keeps one)

Reviewer

  • Useful comments and logging
  • Docs added or updated per the style guide

Acceptance

  • Check for release notes and docs

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

⚠️ Coverage report too large to inline, see the workflow summary.

@Bohreromir
Bohreromir force-pushed the worktree-chore-372-377-feature-flags-helm branch from cca36e1 to b5085de Compare October 23, 2026 14:30
@Bohreromir Bohreromir linked an issue Oct 23, 2026 that may be closed by this pull request
…lags (#372)

Limits and tuning move out of the feature-flag modules into
$lib/client/config (PUBLIC_) and $lib/server/storage/config. All values
are parsed with zod; invalid values stop the server at startup with an
error that names them, instead of silently falling back to defaults.
The config is imported in hooks.server.ts so it is checked at boot.

The legacy alias PUBLIC_STACKABLE_UI_STORAGE_RESTORE_TABS is dropped and
boolean flags only accept true or false.
… tab restore (#372)

PUBLIC_STACKABLE_COCKPIT_STORAGE_TRANSFER_ENABLED replaces the cut/copy,
paste, rename and move flags in the file browser and on the transfer
endpoint. Cut/copy alone had no effect, and the endpoint already treated
the remaining flags as one cost-control switch.

Infinite scroll and tab restore no longer have flags and are always on;
the fixed-row CSV and Parquet preview mode is removed.

BREAKING CHANGE:
PUBLIC_STACKABLE_COCKPIT_STORAGE_{CUT_COPY,PASTE,RENAME,MOVE}_ENABLED,
PUBLIC_STACKABLE_COCKPIT_INFINITE_SCROLL_ENABLED and
PUBLIC_STACKABLE_COCKPIT_STORAGE_RESTORE_TABS are removed.
…vFrom (#372, #377)

features now only holds toggles: trino.completion.enabled,
storage.enabled and the new storage.transfer. Storage limits and tuning,
including archiveCacheMaxMb (previously config.archiveCacheMaxMb), move
to the top-level storage block.

Values are passed through unchanged for the application to validate:
0 and false are no longer dropped, and only whole numbers are converted
to integers.

extraEnv and extraEnvFrom pass additional environment variables to the
container.

Closes #377
@Bohreromir
Bohreromir force-pushed the worktree-chore-372-377-feature-flags-helm branch from b5085de to 8b3a8ee Compare October 23, 2026 14:42
@Bohreromir Bohreromir self-assigned this Oct 23, 2026
@Bohreromir Bohreromir moved this to Development: Waiting for Review in Stackable Engineering Oct 23, 2026
@Bohreromir
Bohreromir marked this pull request as ready for review October 23, 2026 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: Waiting for Review

Development

Successfully merging this pull request may close these issues.

Add DB vars to helm chart Review Feature Flags

1 participant