-
Notifications
You must be signed in to change notification settings - Fork 44
Introduce ability to bypass experiments. More information on Confluence docs and in .md file #699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
wRLSS
wants to merge
1
commit into
master
Choose a base branch
from
feat/ab-testing
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Empty file.
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -28,5 +28,8 @@ | |
| }, | ||
| client: { | ||
| protocol: 'ILC_CLIENT_PROTOCOL', | ||
| }, | ||
| experiments: { | ||
| enabled: 'EXPERIMENTS_ENABLED', | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. prefix with ILC_? Not sure, but it looks like half of the variables follow this convention. |
||
| } | ||
| } | ||
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| import config from 'config'; | ||
| import type { Ruleset, RulesetProvider } from './interfaces'; | ||
| import { validateRuleset } from './validate'; | ||
|
|
||
| /** | ||
| * Current implementation of the experiment ruleset source: reads the ruleset from the | ||
| * static JSON config layer — node-config `experiments.ruleset` (empty in the OSS baseline; | ||
| * populated in a local/registry config layer, or injected in tests). | ||
| * | ||
| * This is the single place that knows where the ruleset comes from. The assignment layer | ||
| * (assign / bucket / consent / cookies / propagation) only ever receives a resolved | ||
| * `Ruleset` and never reads configuration, so the source can evolve on its own. See | ||
| * `docs/ab-testing.md` for a later direction where a remote experiment-management service | ||
| * — a management UI plus SSE/polling delivery — becomes the source of truth, letting | ||
| * stakeholders manage experiments without an ILC deployment. That would arrive as another | ||
| * {@link RulesetProvider} implementation | ||
| * swapped in at `./ruleset`, with no change to the assignment layer — which is the point | ||
| * of keeping the source behind this seam. | ||
| * | ||
| * The read is defensive: a malformed ruleset degrades to "no experiments" rather than | ||
| * crashing ILC bootstrap, and validation problems are surfaced. It runs at construction | ||
| * time — before the app's structured (pino) logger exists — so problems go to stdout. | ||
| */ | ||
| export class StaticConfigRulesetProvider implements RulesetProvider { | ||
| private readonly ruleset: Ruleset; | ||
|
|
||
| constructor() { | ||
| this.ruleset = StaticConfigRulesetProvider.read(); | ||
| } | ||
|
|
||
| public getRuleset(): Ruleset { | ||
| return this.ruleset; | ||
| } | ||
|
|
||
| private static read(): Ruleset { | ||
| if (!config.has('experiments.ruleset')) { | ||
| return {}; | ||
| } | ||
|
|
||
| try { | ||
| const raw = config.get<Ruleset>('experiments.ruleset'); | ||
| const problems = validateRuleset(raw); | ||
| if (problems.length > 0) { | ||
| // eslint-disable-next-line no-console | ||
| console.warn(`[experiments] ruleset has issues:\n ${problems.join('\n ')}`); | ||
| } | ||
| return raw; | ||
| } catch (error) { | ||
| // eslint-disable-next-line no-console | ||
| console.warn('[experiments] failed to load ruleset; running with no experiments', error); | ||
| return {}; | ||
| } | ||
| } | ||
| } |
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a bit expensive operation. I do not see alternative now but it could be a bottleneck potentially