From e71b5433f699f99d46e6817b972c118d6a702987 Mon Sep 17 00:00:00 2001 From: chao-xian Date: Mon, 4 Sep 2023 12:26:58 +0100 Subject: [PATCH] Update ADR-001 to revert status --- docs/ADR/001-porting-to-postgresql.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/ADR/001-porting-to-postgresql.md b/docs/ADR/001-porting-to-postgresql.md index b89e60d9..129411cd 100644 --- a/docs/ADR/001-porting-to-postgresql.md +++ b/docs/ADR/001-porting-to-postgresql.md @@ -38,4 +38,10 @@ This ADR is to outline our decisions and rationale on the steps we take for that ## Status -Accepted \ No newline at end of file +~~Accepted~~ + +Reverted + +On recommendation from the Tech Lead of the Platform Engineering team + +> For simplicity, we came to the conclusion that assuming that the separate postgres version of router-api is running in the background already, and is fully up to date (as in, all changes before it went "live" are synced, plus anything new after the fact), then there is no reason for Router to not just be delivered as normal.