From a06a8d4e9c254f13551b3f77e7207ac8c9346d23 Mon Sep 17 00:00:00 2001
From: Frederick Muriuki Muriithi
Date: Mon, 18 Dec 2023 16:46:57 +0300
Subject: Make Existing Data Public: Close issue

---
 .../make-existing-data-public-view-by-default.gmi                   | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

(limited to 'issues/authentication_authorisation')

diff --git a/issues/authentication_authorisation/make-existing-data-public-view-by-default.gmi b/issues/authentication_authorisation/make-existing-data-public-view-by-default.gmi
index 0f11371..5f3cbf0 100644
--- a/issues/authentication_authorisation/make-existing-data-public-view-by-default.gmi
+++ b/issues/authentication_authorisation/make-existing-data-public-view-by-default.gmi
@@ -4,12 +4,16 @@
 
 * assigned: fredm, zsloan, zachs
 * priority: medium
-* status: open
+* status: closed, completed
 * keywords: authentication, authorisation, oauth2, data migration
 * type: migration
 
 ## Description
 
+A script was built for this and has been already been used.
+
+----
+
 From the information coming to light, all the "current data" needs to be publicly visible. There is therefore need to implement a temporary script that will be manually run to organise the data into resources and user groups and assign the appropriate privileges.
 
 The script could:
-- 
cgit v1.2.3