What to do with records.py
#18
Honestpuck
started this conversation in
Ideas
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? |
2 replies
|
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. |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
After our discussion about
records.pyand 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
requestscalls were replaced by the python-jamf API calls we might have something.If people like this idea I'll tackle it this week.
All reactions