Closed Bug 1075170 Opened 11 years ago Closed 11 years ago

Please deploy browserid-verifier 0.2.4 to production

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Product:
Cloud Services
Component:
Operations: Deployment Requests - DEPRECATED
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: kthiessen, Unassigned)

References

Details

(Whiteboard: [qa+])

Please deploy the packages agreed on in Bug #1069748 to production, and document in this ticket which versions/SHAs were deployed. +++ This bug was initially created as a clone of Bug #1069748 +++ This version of browserid-verifier includes a change to log output formatting, to put potential PII as top-level fields on the JSON log rather than as fields of an embedded JSON string: https://github.com/mozilla/browserid-verifier/pull/63 It should help with Bug 1053959 Comment 9 and similar. Please deploy v0.2.4 to stage for both tokenserver-local and standalone verifier stacks. As it's just a logging format change, a light load and sanity test should be sufficient for deployment.
Both fxa-browserid-verifier (verifier.accounts.firefox.com) and tokenserver with 0.2.4 of verifier (token.services.mozilla.com) are deployed. Please quickly verify the changes. DNS should be updated by now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Quick verification done yesterday afternoon, but I ran out of time to document it.
Status: RESOLVED → VERIFIED
QA Contact: kthiessen
You need to log in before you can comment on or make changes to this bug.