feat: ensure that projects have consistent ids (#8)

This change adjusts how shadow projects are stored in the database. When a project is created, it is looked up using the name and when not found keystone would normally assign it a random UUID. This ensures that all projects have a consistent hash when being assigned which will ensure that project IDs remain consistent between regions. Signed-off-by: Kevin Carter <[email protected]>
rackerlabs · Feb 1, 2025 · 3207641 · 3207641
1 parent 319811a
commit 3207641
Showing 1 changed file with 5 additions and 3 deletions.
diff --git a/keystone_rxt/rackspace.py b/keystone_rxt/rackspace.py
@@ -298,7 +298,9 @@ def _handle_projects_from_mapping(
                 },
             )
             project_ref = {
-                "id": mapped.uuid.uuid4().hex,
+                "id": hashlib.sha224(
+                    shadow_project["name"].encode("utf-8")
+                ).hexdigest(),
                 "name": shadow_project["name"],
                 "domain_id": shadow_project["domain"]["id"],
             }
@@ -328,8 +330,8 @@ def _handle_projects_from_mapping(
 
         metadata = shadow_project.get("metadata", list())
         for item in metadata:
-            if item['key'] not in project:
-                project[item['key']] = item['value']
+            if item["key"] not in project:
+                project[item["key"]] = item["value"]
                 update_needed = True
 
         if update_needed: