Bug 956444 - handle migration sentinel

[ncalexan]

This embraces and extends @rnewman's earlier work.

[rnewman]

I honestly don't remember writing any of this, so heh.

Looks good to me. I'd like to see some kind of measurement of this: whether that's telemetry, FHR, or something as simple as a URL parameter or object uploaded to the new Sync account, doesn't matter.

[ncalexan]

On Mon, Dec 22, 2014 at 10:47 AM, Richard Newman [email protected] wrote:

I honestly don't remember writing any of this, so heh.

It was a long time ago.

Looks good to me. I'd like to see some kind of measurement of this: whether that's telemetry, FHR, or something as simple as a URL parameter or object uploaded to the new Sync account, doesn't matter.

That's tricky. Calling telemetry from background services is kinda-sorta uncharted territory: neither of us wrote the telemetry stuff for the Search Activity and frankly I don't trust it. Configuring FHR during a Sync requires some machinations that I once worked out (I think?) but were non-trivial. Uploading an object to the new Sync account is do-able, but the most obvious one is to include something in the client record, which is transient. I suppose it would be possible to upload to a new migrated collection. I wonder if it would make sense to try to use the fxa mechanism where we add some tracking data to the /account/login call. It's a little disjointed and delayed, but it might be possible.

If you can show how to arrange for FHR to be configured correctly during a (Firefox Account) Sync, that would be best.