From 0c4481a83054cc163dadd993c7362fa86ea2283f Mon Sep 17 00:00:00 2001
From: Brian Veltman <2551674+brianveltman@users.noreply.github.com>
Date: Sat, 9 Nov 2024 17:25:30 -1000
Subject: [PATCH] Add todos

---
 docs/README.md | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/docs/README.md b/docs/README.md
index a87c1f8..a94d1ba 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -1,3 +1,22 @@
 When using this in a 'desired-state' kind of way, renaming repositories is not supported. This has to do with the fact when you rename a repository, it will be considered a new repo and the old one will be deleted since its not in the list of 'desired repos' anymore.
 
-Unfortunatly repos do not have an unique identifier that's returned by the Nexus API, therefore we can not use that to update a new of a repo.
\ No newline at end of file
+Unfortunatly repos do not have an unique identifier that's returned by the Nexus API, therefore we can not use that to update a new of a repo.
+
+
+Take away: when not all attributes for PUT are passed through the API, the role might see it as changed, eventho its not.
+
+if the order of the roles/privileges changes, it will not be updated, but it will try to PUT all the changes to the api
+
+
+# TODO:
+- ALL repository endpoints
+- Email endpoint
+- Blob store endpoint
+- HTTPS System settings
+- Security Mangement Anonymous Access
+- Security Management LDAP
+- Security Management REALMS
+- Security Management Privileges
+- Security Management Roles
+- Security Certificates
+- Tasks