docs: add handleCsrReplicationEvent

docs/example.md

@@ -0,0 +1,19 @@
+# Title:
+
+## Status: 
+(accepted | rejected | proposed | deprecated)
+
+## Context: 
+(what is our problem)
+
+## Decision: 
+(how it will affect app or individual parts of the app)
+
+## Consequences: 
+(how it will affect app or individual parts of the app)
+
+## Code location: 
+(package->file)
+
+## Date: 
+(dd.mm.rrrr)

docs/handleCsrReplicationEvent.md

@@ -0,0 +1,20 @@
+# Title: 
+Handle possibility of multiple replication events in certificate requests at the same time
+
+## Status: 
+accepted
+
+## Context: 
+Kinga discovered a bug where when the owner is offline and several (3) users with the same name have joined, sometimes the owner can register two users with the same name
+
+## Decision: 
+Introducing a locking mechanism to prevent the next event from being processed if the previous one is still being processed
+
+## Consequences: 
+We added queue concept and events will be processed individually in chronological order
+
+## Code location: 
+backend -> storage.service.ts
+
+## Date: 
+07-11-2023

packages/backend/src/nest/storage/storage.service.ts

@@ -432,6 +432,7 @@ export class StorageService extends EventEmitter {
       },
     })
 
+    // DOCS -> handleCsrReplicationEvent.md
     this.certificatesRequests.events.on('replicated', async () => {
       this.logger('REPLICATED: CSRs')