Closed data-sync-user closed 4 years ago
I did find one obscure spot we missed, and updated the auth-server docs with another missed update:
New endpoints specific to AET
Profile server
GET /v1/ecosystem_anon_id
POST /v1/ecosystem_anon_id
routes.ecosystem_anon_id.post
route headerAuth server
PUT /account/ecosystemAnonId
log.begin('account.updateEcosystemAnonId')
callAuth-db server
PUT /account/:uid/ecosystemAnonId
The eco_anon_id otherwise flows from auth-db to auth via the existing account-related GET calls, and from auth to profile via the existing GET _core_profile call.
We should verify that all the correct metrics are logged for the new AET feature. This includes events for creation, deletion, updated etc.
┆Issue is synchronized with this Jira Task ┆Issue Number: FXA-1909