What to do with records.py
#18
Replies: 2 comments 5 replies
-
So if I understand correctly, in this file _JPC is equivalent to API and JPCObject is equivalent to Record. So JPCObject subclasses _JPC. To make ours do the same, then Record would subclass API, right? Is that what you are proposing? |
Beta Was this translation helpful? Give feedback.
-
Here is the Jamf objects from records.py we are going to focus on (not listed in priority order).
I don't plan on deserializing any of them in the code, but instead I'm going to write a bunch of demo/test code that actually does things we want like create new objects, list them, modify them, delete them etc. I'll probably try to simulate all of the things I do with the GUI first. |
Beta Was this translation helpful? Give feedback.
-
After our discussion about
records.py
and what it might need I remembered some code I wrote a while back while playing around with JP.Here it is. I think it might offer a solution or at least a framework for one. I think the important thing about this idea is the way it simplifies the call structure without adding much complexity. If the
requests
calls were replaced by the python-jamf API calls we might have something.If people like this idea I'll tackle it this week.
Beta Was this translation helpful? Give feedback.
All reactions