Modify rappor parameters.

components/rappor/rappor_pref_names.cc

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "components/rappor/rappor_pref_names.h"
 
 namespace rappor {
 namespace prefs {
 
-// A randomly generated number, which determines cohort data is reported for.
-const char kRapporCohort[] = "rappor.cohort";

[Alexei Svitkine (slow), 2014/05/20 06:59:49]

Keep the old pref and add code to Clear it, so that clients' prefs won't be
littered with old prefs. Then, after a few releases, remove code related to it.

[Steven Holte, 2014/05/20 18:28:03]

Is there a reliable pattern for doing a one time Clear of data, so that I can
ensure this only gets re-rolled once?

[Alexei Svitkine (slow), 2014/05/21 09:13:37]

Renaming the pref key the correct way to do this, but also keeping an entry for
the old name, i.e.:

const char kRapporCohortSeed[] = "rappor.cohort_seed";
// comment about it:
const char kRapporCohortDeprecated[] = "rappor.cohort";

And in your code that reads the new pref also clear the old pref.

See also metrics_state_manager.cc which does this for some prefs (e.g.
kMetricsOldLowEntropySource).

[Steven Holte, 2014/05/21 19:02:57]

Done. PTAL.

+// A randomly generated number, which determines cohorts data is reported for.
+const char kRapporCohortSeed[] = "rappor.cohort_seed";
 
 // A base-64 encoded, randomly generated byte string, which is used as a seed
 // for redacting collected data.
 // Important: This value should remain secret at the client, and never be
 // reported on the network, or to the server.
 const char kRapporSecret[] = "rappor.secret";
 
 }  // namespace prefs
 }  // namespace rappor