Expose Merino's endpoint to Nimbus
Categories
(Firefox :: Address Bar, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox105 | --- | fixed |
People
(Reporter: nanj, Assigned: adw)
References
Details
Attachments
(1 file)
To allow us to do rapid feature development for Firefox Suggest, we've rewritten Merino with a Python tech-stack called Merino-py. As part of the migration, we're planning to put this new service behind a new endpoint, (e.g. 'merinopy.services.mozilla.com') and then run a series of experiments to ensure that merino-py can offer the same user experience as merino.
To support that, we'd like to make the merino endpoint Nimbus controllable.
Once merino-py is ready to serve all the traffic in production, we will then migrate from merino to merino-py using the same endpoint i.e. merino.services.mozilla.com.
|
Assignee | |
Updated•2 years ago
|
|
|
Assignee | |
Updated•2 years ago
|
|
|
Assignee | |
Comment 1•2 years ago
|
||
Turns out I added this same merinoEndpointURL variable back in D123707 but
removed it from the final version. But I forgot to remove the corresponding test
code here, so this is actually already tested. Apparently
ExperimentFakes.enrollWithFeatureConfig() lets you set values for Nimbus
variables that don't exist and it just works.
I forgot to remove the similar merinoEndpointParamQuery variable from the test
too, so I've removed that now. It's not declared in FeatureManifest or used
anywhere.
This also updates the Nimbus owner for urlbar to the new team email address.
Pushed by dwillcoxon@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5b2d6c058f77 Expose Merino's endpoint to Nimbus. r=nanj
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Description
•