Closed
Bug 1225380
Opened 10 years ago
Closed 10 years ago
Please deploy autopush 1.8.1 to PRODUCTION
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rpapa, Assigned: oremj)
References
Details
************************************
RELEASE NOTES
************************************
https://github.com/mozilla-services/autopush/releases
COMPARISONS
https://github.com/mozilla-services/autopush/compare/1.7.1...1.7.2
https://github.com/mozilla-services/autopush/compare/1.7.2...1.8.0
https://github.com/mozilla-services/autopush/compare/1.8.0...1.8.1
TAGS
https://github.com/mozilla-services/autopush/releases/tag/1.8.1
https://github.com/mozilla-services/autopush/commit/7025e1d1293e85f35dedb2bcba214fc3bb881c3b
CHANGELOG
1.8.1 (2015-11-16)
==================
Features
--------
* Convert proprietary AUTH to use Bearer Token for client REST interfaces.
Issue #238.
Bug Fixes
---------
WebPush
-------
Configuration Changes
---------------------
* Please include the new `--auth_key` which is the base token set for
generating bearer tokens. This uses the same format as the `--crypto_key`,
but should be a different value to prevent possible key detection. The key
can be generated using the same `bin/autokey` tool used to generate the
crypto_key
1.8.0 (2015-11-13)
==================
Features
--------
* Server provided SenderID values for GCM router using clients
The GCM router will randomly select one of a list of SenderIDs stored in
S3 under the "oms-autopush"/"senderids" key. The values can
be loaded into S3 either via the S3 console, or by running an instance of
autopush and passing the values as the "senderid_list" argument. Issue #185.
* REST Registration will now return a valid ChannelID if one is not specified.
Issue #182.
* Add hello timeout. Issue #169.
* Convert proprietary AUTH to use HAWK for client REST interfaces. Issue #201.
* Add DELETE /uaid[/chid] functions to client REST interfaces. Issue #183.
* Add .editorconfig for consistent styling in editors. Issue #218.
* Added --human_logs to display more human friendly logging.
* If you specify the --s3_bucket=None, the app will only use local memory
and will not call out to the S3 repository. It is STRONGLY suggested that
you specify the full --senderid_list data set.
* You may now specify multiple keys for the crypto_key value. Values should
be a list ordered from newest to oldest allowed key.
Bug Fixes
---------
* Capture all ProvisionedException errors in websocket and endpoint correctly.
Issue #175.
* Clean-up several recent deferToLater calls that didn't have their cancelled
exceptions ignored. Issue #208.
* Fix improper attribute reference in delete call. Issue #211.
* Always include TTL header in response to a WebPush notification. Issue #194.
* Increased unit test coverage due to removal of proprietary AUTH.
* Fixed issue with local senderid data cache. (discovered while debugging.)
WebPush
-------
Backwards Incompatibilities
---------------------------
* Do not specify values for boolean flags.
* 'cors' is now enabled by default. In it's place use --nocors if you wish
to disable CORS. Please remove "cors" flag from configuration files.
* Do not specify --gcm_apikey. Instead, store the API key and senderid as
values in S3. The data may still be written as a JSON string such as:
' "`_senderID_`": {"auth": "`_api_key`"}}'
activate the GCM bridge by specifying --gcm_enabled.
Reporter | ||
Comment 1•10 years ago
|
||
We'll be deploying this release on Wed., 11/18 @2p
Reporter | ||
Comment 2•10 years ago
|
||
We'll be deploying 1.8.1 release to production in a few minutes.
currently on production (pre-deployment)
----------------------------
URL CHECKS (PROD)
----------------------------
https://updates.push.services.mozilla.com:
Response time: 0.139788
https://updates.push.services.mozilla.com/health:
{
"status": "OK",
"prod.autopush.storage": {
"status": "OK"
},
"version": "1.7.2",
"clients": 0,
"prod.autopush.router": {
"status": "OK"
}
}
Response time: 0.14441
https://updates.push.services.mozilla.com/status:
{
"status": "OK",
"version": "1.7.2"
}
Response time: 0.131306
Reporter | ||
Comment 3•10 years ago
|
||
:oremj has deployed this release to production and DNS has been switched.
E2E TESTS
Able to successfully ring, lock Flame device (w/ B2G 2.2) using findmydevice application x10
Able to place several Hello (Loop) calls successfully and verify e2e test calls using room status changes, pop notifications
FF desktop pop notification tests passing on services-qa automation
Verifying this release
----------------------------
URL CHECKS (PROD)
----------------------------
https://updates.push.services.mozilla.com/health:
{
"status": "OK",
"prod.autopush.storage": {
"status": "OK"
},
"version": "1.8.1",
"clients": 0,
"prod.autopush.router": {
"status": "OK"
}
}
Response time: 0.140511
https://updates.push.services.mozilla.com/status:
{
"status": "OK",
"version": "1.8.1"
}
Response time: 0.131797
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•10 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•