Skip to content

remove JSON file flag data source - #840

Merged
justindbaur merged 1 commit into
mainfrom
remove-flags-json-file
Jul 30, 2026
Merged

remove JSON file flag data source#840
justindbaur merged 1 commit into
mainfrom
remove-flags-json-file

Conversation

@justindbaur

Copy link
Copy Markdown
Member

🎟️ Tracking

bitwarden/server#7898

📔 Objective

Removes documentation for the flags.json file-based data source for local feature flag configuration, which is no longer supported after the server change linked above.

📸 Screenshots

N/A

Removes documentation for the flags.json file-based data source following
bitwarden/server#7898 which dropped support for it.
@justindbaur justindbaur changed the title docs: remove JSON file flag data source remove JSON file flag data source Jul 30, 2026
@justindbaur
justindbaur marked this pull request as ready for review July 30, 2026 15:31
@justindbaur
justindbaur requested a review from a team as a code owner July 30, 2026 15:31
@github-actions

github-actions Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

This documentation-only change removes the flags.json file-based data source from
docs/contributing/feature-flags.md, consistent with the linked server change
(bitwarden/server#7898) which confirms FlagDataFilePath is no longer supported. The flag source
table, the self-hosted caution admonition, and the surrounding prose were all updated together, so
no stale references to the file-based source remain in the page. I verified no other docs page links
to the removed Local configuration: JSON file section anchor, and that the remaining user secrets
example (globalSettings.launchDarkly.flagValues) is still a supported configuration path per the
server PR's backward-compatibility notes.

No findings.

@justindbaur
justindbaur merged commit 74f3626 into main Jul 30, 2026
16 checks passed
@justindbaur
justindbaur deleted the remove-flags-json-file branch July 30, 2026 18:36
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