Closed Bug 1673945 Opened 7 months ago Closed 6 months ago

Please deploy Autopush-rs 1.57.0 to STAGE

Categories

(Cloud Services :: Operations: Autopush, task)

task

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jrconlin, Assigned: oremj)

Details

1.57.0 (2020-10-16)

https://github.com/mozilla-services/autopush-rs/releases/tag/1.57.0

Operation Notes:

This release includes the autopush-endpoint function into the main rust autopush. This will require configuration of a docker endpoint handler.

Please contact :jrconlin with questions or clarifications.

Features

  • Include minimal debug info in release builds (#215) (fd659e3e, closes #77)
  • Support "gcm" as an alias to "fcm" (#211) (fd0d63d2, closes #204)
  • Add the log-check route and remove unused ApiError variants/impls (#209) (1b0b18b3, closes #208)
  • Amazon Device Messaging router (#207) (c587446a, closes #165)
  • Use autoendpoint-rs in integration tests (#205) (31d2d19c, closes #168)
  • Add the unregister user route (#195) (b4bb1636, closes #179)
  • APNS Router (#201) (ce51957f, closes #164)
  • New channel endpoint (#189) (6cc9a7dc)
  • Update token endpoint (#188) (bb395fb2, closes #177)
  • Sentry integration for autoendpoint (#196) (674d7d2c, closes #155)
  • Delete message endpoint (#186) (6a7fa492, closes #175)
  • User registration (#185) (6df3e36b, closes #176)
  • Route notifications to FCM (Android) (#171) (d9a0d9d7, closes #162)
  • Route notifications to autopush connection servers (#167) (e73dff17, closes #161)
  • Return detailed autoendpoint errors (#170) (91d483ab, closes #159)
  • Record the encoding in a metric if there is an encrypted payload (#166) (8451d3f9)
  • Validate autoendpoint JWT tokens (#154) (04fee7f9, closes #103)
  • Validate user subscription data in autoendpoint (#160) (8efa42c8, closes #156)
  • Basic autoendpoint extractors (#151) (b08fdbdd)

Bug Fixes

  • enforce VAPID aud (#225) (e3963262)
  • Fix debug info setting being ignored (#219) (35a9d4f6)
  • Check the max data size against the final message payload (#212) (4e07ff07, closes #203)
  • Drop 0 TTL WebPush notifications if they aren't delivered the first time (#210) (a28cb295)
  • Fix having extra slashes in the endpoint URL (#206) (f943659e)
  • Drop unknown FCM users (#197) (068f54dd, closes #173)
  • Strip padding and double quotes from encryption and crypto-key headers (#200) (e20fc6af, closes #192)
  • Copy and upgrade parts of DynamoStorage into autoendpoint (#174) (120a46b7, closes #172)
  • Use errnos from validation errors (#184) (147aed84)

Doc

  • Add a fernet_key.py script for generating Fernet keys (#218) (aa0e9d96, closes #217)
  • Add a sample config for autopush and fix some settings (#216) (5badbfbe)
  • Add a sample config for autoendpoint and normalize router settings (#214) (3b30d694)

Chore

configuration

All configuration can be specified as ENV vars (prefixed by "AUTOEND_")

The following settings are available:

  • AUTOEND_HOST Public Host name to use in endpoint URLs default 127.0.0.1
  • AUTOEND_SCHEME Public scheme to use in endpoint URLs default https
  • AUTOEND_PORT Public port to use in endpoint URLs default based on AUTOEND_SCHEME
  • AUTOEND_CRYPTO_KEYS JSON like list of key strings (e.g. [abc123, def456]) for endpoint decryption
  • AUTOEND_AUTH_KEYS JSON like list of key strings for auth token generation
  • AUTOEND_STATSD_HOST default NONE
  • AUTOEND_STATSD_PORT default 8125
  • AUTOEND_STATSD_LABEL default autoendpoint

Include these to activate these services.

  • AUTOEND_FCM.CREDENTIALS FCM credential string (e.g. {"project_id": "abc123", "auth_file": "/abc/123"} )
  • AUTOEND_APNS.CREDENTIALS (e.g. {"channel_name": {"cert": "/abc/123", "key": "/abc/456", "topic":..., "sandbox":...}, ...} )
  • AUTOEND_ADM.CREDENTIALS

Additional options can be discovered by looking in the source code

This is nearly complete. Currently blocked on: https://github.com/mozilla-services/autopush-rs/issues/240 We can work around it, but I think it will end up being less work to alter the app than to work around.

Replaced by Bug 1680361

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.