* Set a default value of `allowed_metrics_flow_cors_origins` to `null`
* Change the default value of `pairing.server_base_uri` to
`wss://dev.channelserver.nonprod.cloudops.mozgcp.net` which is used
by all dev boxes. Production config will need to be updated to handle
this change.
fixes#7066
BREAKING CHANGE
Originally added in 62f4b637, then reverted in e64c571b because it broke
fxa-dev. That breakage was caused by missing Redis config for backoff
and retry, and a too-low limit on pending connections. Those required
config tweaks are added in the next commit.
Feature-flagging caused fxa-dev to fail with Redis connection errors.
Let's back it out from `master` while I dig into what's going wrong.
This reverts commit 62f4b63709.
Hot on the heels of #6895, it's now relatively pain
free to deprecate a context.
This deprecates `context=fx_desktop_v2` which hasn't
been used since Firefox 45, 20 versions ago.
Users will instead be prompted to upgrade their
Firefox.
fixes#7030
Follow on to #44 that added logging only query parameter validation to GET /metrics-flow. This causes validation errors to reject the request.
fixes bz1528793
I was calling logger.info with a single object containing an `op` field
in get-metrics-flow.js when query parameter validation errors occurred.
@jbuck informed me that 'request.metrics-flow.invalid-param' should
be the first parameter to logger.info and the rest of the object
the 2nd.
parameter validation was added after several important
pages were already calling this endpoint. To avoid causing any of those pages
to error out, log and swallow any validation errors. If no errors are logged,
then we can change to return an error.
fixes bz1528793
Mozilla China's FxA stack does not need COPPA. So that
they don't have to remove it every time we update our
code, this puts the feature behind a feature flag.
In configuration, coppa.enabled set to `false` will disable COPPA.
fixes#6736
The amplitude import needs a device id (or a user id) on each event,
otherwise they're treated as invalid. We have code on the client side
for generating it in lib/app-start.js, but the events generated on the
server are not currently making it to Amplitude. This change adds an
equivalent device id for those events too.
* firefox-profile to 1.2.0
* grunt-conventional-changelog to 6.0.0
* grunt-htmllint to 0.3.0
Remove grunt-contrib-sasslint, it wasn't being
called by anything and we have sass-lint that is actually run.
Shane Tomlinson
hritvi
Phil Booth
Muhammad Farhan
Hector Zhao
Jon Buckley
vladikoff
Vijay Budhram
Ryan Kelly
irrationalagent