influxdata / influxdata/influxdb
Migrate feature flags to the backend
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
We currently have a lot of feature flags that exist only in the browser, meaning our fellow engineers on the backend only have a small glimpse into what's possible with the product. These are all defined here:
https://github.com/influxdata/influxdb/blob/master/ui/src/shared/selectors/flags.ts
the more of the OSS flags we move here:
https://github.com/influxdata/influxdb/blob/master/flags.yml
and Cloud flags we move here:
https://github.com/influxdata/idpe/blob/master/flags.yml
the better we can share functionality and unify logging across our services.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying the browser-only flags in ui/src/shared/selectors/flags.ts, then compare them with flags.yml in influxdb and the linked Cloud flags.yml. Determine which OSS and Cloud flags belong in the backend locations and how the shared logging goal applies. Done means the applicable flags are represented in the backend configuration and functionality is shared across services.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100