Jens
faeb58ef6d
GeoIntel release gates / Compile, test, contracts and builds (push) Successful in 1m49s
GeoIntel release gates / Python and npm vulnerability policy (push) Successful in 21s
GeoIntel release gates / Production AI image, SBOM and container scan (push) Successful in 5m39s
GeoIntel release gates / Deploy exact gated revision to Unraid (push) Failing after 58m43s
35 lines
870 B
Markdown
35 lines
870 B
Markdown
# Feature Flag Strategy
|
|
|
|
Feature flags prevent future modules from appearing as broken V1 features.
|
|
|
|
## Required Flags
|
|
- `ENABLE_GRB_CONNECTOR`
|
|
- `ENABLE_OSM_CONNECTOR`
|
|
- `ENABLE_SENTINEL_LAB`
|
|
- `ENABLE_SAM_SEGMENTATION`
|
|
- `ENABLE_YOLO_DETECTION`
|
|
- `ENABLE_LIDAR_LAB`
|
|
- `ENABLE_TRAINING_STUDIO`
|
|
- `ENABLE_QGIS_EXPORT`
|
|
|
|
## V1 Defaults
|
|
```env
|
|
ENABLE_GRB_CONNECTOR=true
|
|
ENABLE_OSM_CONNECTOR=true
|
|
ENABLE_SENTINEL_LAB=false
|
|
ENABLE_SAM_SEGMENTATION=false
|
|
ENABLE_YOLO_DETECTION=true
|
|
ENABLE_LIDAR_LAB=false
|
|
ENABLE_TRAINING_STUDIO=false
|
|
ENABLE_QGIS_EXPORT=false
|
|
```
|
|
|
|
## UI Behavior
|
|
Disabled features may be visible as roadmap cards, but must not look like broken tools. They should show:
|
|
- why disabled;
|
|
- what dependency is missing;
|
|
- which milestone enables them.
|
|
|
|
## Backend Behavior
|
|
Disabled endpoints return a typed `FEATURE_DISABLED` error, not 404 and not silent success.
|