vault backup: 2026-09-10 14:55:50
This commit is contained in:
+75
@@ -0,0 +1,75 @@
|
||||
---
|
||||
date: 2026-09-10
|
||||
status: proposed
|
||||
owner: Amadou
|
||||
project: "[[Boukili]]"
|
||||
---
|
||||
---
|
||||
|
||||
|
||||
> 🟡 **Proposed** · 🟢 **Decided** · 🔴 **Rejected** · ⚫ **Superseded**
|
||||
|
||||
## Context
|
||||
|
||||
Why is a decision needed?
|
||||
|
||||
The details of these items are in the emails we have exchanged.
|
||||
|
||||
1. user_last_activity_at fallback
|
||||
|
||||
2. Contentful blacklist -- for controlling notifications
|
||||
|
||||
3. Firebase auth lockout
|
||||
|
||||
4. Migration update messaging
|
||||
|
||||
Il y a un potentiel regression ou Salesforce n'est plus la source de vérité
|
||||
Pas de plan de tests une fois la migration en place
|
||||
Que faire si un utilisateur se connecte sur un appareil et migre. Puis change d'appareil qui n'a pas le auto-update, le compte sur cette appareil sera sous firebase et donc l'utilisateur n'aura pas de synchro entre le nouveau aws et le firebase.
|
||||
|
||||
|
||||
|
||||
## Decision
|
||||
|
||||
What was decided?
|
||||
|
||||
## Why
|
||||
|
||||
Why was this option chosen?
|
||||
|
||||
-
|
||||
|
||||
## Consequences
|
||||
|
||||
What are we accepting by making this decision?
|
||||
|
||||
-
|
||||
|
||||
## Related
|
||||
|
||||
-
|
||||
|
||||
|
||||
---
|
||||
|
||||
## Options Considered _(optional)_
|
||||
|
||||
### Option 1
|
||||
|
||||
**Description:**
|
||||
|
||||
**Pros:**
|
||||
-
|
||||
|
||||
**Cons:**
|
||||
-
|
||||
|
||||
### Option 2
|
||||
|
||||
**Description:**
|
||||
|
||||
**Pros:**
|
||||
-
|
||||
|
||||
**Cons:**
|
||||
-
|
||||
Reference in New Issue
Block a user