Update 7/4

notes.org_archive

@@ -314,3 +314,61 @@ Cluster api - failed provision
 :ARCHIVE_CATEGORY: notes
 :ARCHIVE_TODO: DONE
 :END:
+
+* DONE Figure out why api-internal is stuck
+:PROPERTIES:
+:ARCHIVE_TIME: 2023-07-04 Tue 13:04
+:ARCHIVE_FILE: ~/org-notes/notes.org
+:ARCHIVE_OLPATH: Tasks
+:ARCHIVE_CATEGORY: notes
+:ARCHIVE_TODO: DONE
+:END:
+ problem: Still in INIT after 11m
+   node: Successfully assigned api/api-internal-697b64c8b7-vfwrh to prod-ny5-core-09
+ api-internal was missing NATS configuration, db:seed was triggering NATS events
+
+* TODO Keep going with Infratographer events
+:PROPERTIES:
+:ARCHIVE_TIME: 2023-07-04 Tue 13:08
+:ARCHIVE_FILE: ~/org-notes/notes.org
+:ARCHIVE_OLPATH: Tasks
+:ARCHIVE_CATEGORY: notes
+:ARCHIVE_TODO: TODO
+:END:
+  - The papertrail gem lets you know what changed
+    `o.versions.first.object_changes` yields the last set of saved changes
+  - Need to whitelist which fields are shareable
+  - Plan, take the raw change set
+  - Reduce changeset to whitelisted fields
+  - Emit that change set to infratographer.
+  - Try to figure out what the event structure for a membership being added means.
+
+  Revision: We ditched the changes and just slapped the object IDs
+  in the event.
+
+  This is actually a good move. By just generating event by the ID we
+  reduce the chance that consumers depend on the state of an object
+  instead of just the ID.
+
+* DONE Keep going with Infratographer events
+:PROPERTIES:
+:ARCHIVE_TIME: 2023-07-04 Tue 13:09
+:ARCHIVE_FILE: ~/org-notes/notes.org
+:ARCHIVE_OLPATH: Tasks
+:ARCHIVE_CATEGORY: notes
+:ARCHIVE_TODO: DONE
+:END:
+  - The papertrail gem lets you know what changed
+    `o.versions.first.object_changes` yields the last set of saved changes
+  - Need to whitelist which fields are shareable
+  - Plan, take the raw change set
+  - Reduce changeset to whitelisted fields
+  - Emit that change set to infratographer.
+  - Try to figure out what the event structure for a membership being added means.
+
+  Revision: We ditched the changes and just slapped the object IDs
+  in the event.
+
+  This is actually a good move. By just generating event by the ID we
+  reduce the chance that consumers depend on the state of an object
+  instead of just the ID.