1795780 - Make it possible to disable migrators while they're under development and testing

Status: RESOLVED FIXED

(Firefox :: Migration, enhancement)

Description

[Mike Conley (:mconley) (:⚙️)]

We have several students working on new migrators. We should make it possible to easily disable those migrators while they're being tested and refined, so that we can only enable and ship them when we're more confident that they're ready.

Comment 1

[Mike Conley (:mconley) (:⚙️)]

Attachment: Bug 1795780 - Add the ability to disable a browser migrator at runtime via a pref. r?Gijs!

It seems that at build time, we already make decisions about what migrators we register
with XPCOM in browser/components/migration/components.conf. This doesn't, however, give
us the ability to turn off a migrator that happens to be misbehaving, nor make it easy
for us to do development of a new migrator without exposing it to the migration dialog
(without doing binary recompiles).

This adds another layer to the enable-ment of our migrators so that they must both
be registered AND enabled in order to appear in the import dialog.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/500284b77862
Add the ability to disable a browser migrator at runtime via a pref. r=NeilDeakin,Gijs

Comment 3

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/500284b77862