[AXON-1673] chore: move FF overrides into static config #1409
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sdzh-atlassian
requested review from
Blastoplex,
amarg-at,
bhorai-atl,
bwieger-atlassian-com,
cabella-dot,
ccallcottstevens,
dchiew-atl,
jwang19-atlassian,
marcomura,
matt-lassian,
om-ukr,
sspanchenko and
teg-atlassian
as code owners
![atlassian[bot]](https://avatars.githubusercontent.com/in/14320?s=60&v=4){kind=small}
sdzh-atlassian
commented
Dec 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What Is This Change?
Another step in centralizing our
process.envusage - moved the feature flag override logic into static config, and the parsing - to a separate file. Added extra tests and documentationThere are now 3 ways to add an override:
.env, if you'd like to persist the change in your local workspace* - expected format is documented* - the .env update currently requires a full re-build, will fix this in another PR
This specifically relates to overrides, so normal FF client logic isn't affected
How Has This Been Tested?
See demo:
https://www.loom.com/share/5cfdbe8832aa4584a57ac0c81d25610f
Basic checks:
npm run lintnpm run test