LW-13680 Add FF_OVERRIDE env variable to locally override feature flags

[iccicci]

Checklist

• JIRA - LW-13680
• Proper tests implemented
• Screenshots added.

---

Proposed solution

Proposed the approach of a JSON encoded variable as after WebPack build we no longer have the power to dynamically access process.env.

Following code

for (const i of [1, 2, 3, 4]) console.log('feature', i, process.env[`FEATURE_${i}`]);
console.log('feature1', process.env.FEATURE_1);
console.log('feature2', process.env.FEATURE_2);
console.log('feature3', process.env.FEATURE_3);
console.log('feature4', process.env.FEATURE_4);

produces following logs

feature 1 undefined
feature 2 undefined
feature 3 undefined
feature 4 undefined
feature1 undefined
feature2 test
feature3 undefined
feature4 false

Proposed parsing as boolean as all FF have a boolean value. Ref: isFeatureFlagEnabled

Testing

Manually tested

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[lace-bot]

Allure Report

allure-report-publisher generated test report!

processReports: ✅ test report for 427c988f

	passed	failed	skipped	flaky	total	result
Total	33	0	4	0	37	✅