Missing functionnality

Hi 👋 ,

Looking to please request tvos compatibility to pull in data from our Jamf instance to Apple TV Dashboard.

Platform syntax in podfile: platform :tvos, '10.0'

pod install returns:

[!] The platform of the target `Dashboard` (tvOS 10.0) is not compatible with `JAMFKit (0.3.0)`, which does not support `tvos`

Thank you! :)

Miscellaneous

Information | Value | ------------------------------|------------------------------| Language | Swift Platform | tvOS Platform version | 10.0 JamfKit version | latest as of March 3rd 2018 Package manager | CocoaPods Package manager version | 1.3.1 XCode version | 9.2

New feature

Short description

Users of JamfKit can make the request toward the Jamf host on their own accord and simply pass the extracted JSON with the objects supplied by JamfKit to obtain instances of these.

But, to ease the development process, JamfKit can also supply the output of the request needed for each single object.

Missing functionnality

Users should be able to configure the current Jamf host parameters which are going to be used to preconfigure the URLRequest used by JamfKit.

Once the host configuration is fully completed (host, port, username, password) a singleton will allow users to retrieve the following for each type of object:

• the fully configured (verb, url, headers, parameters, body) URLRequest for performing a request with the framework of their choice (they'll take care of parsing the result)
• the output of the same request, everything related to JSON deserialization is taken care of, the result could be a single object, some objects or simply an error

Implementation

First off, JamfKit needs to supply a way of configuring the host, this can be done through a Singleton.

Once configuration is done, the same manager can supply different types of request based on each JSS objects (some endpoints are read-only, others are CRUD ready) for the users to consume with the framework of their choice (AFNetworking, Moya, Alamofire, NSURLSession, etc.).

The library could also perform NSURLSession requests for the user and simply return the instances of the objects that are expected from the request or an error if something went wrong.

Short description

The Building model is out of sync with the Jamf Pro API object.

Missing functionnality

Some fields are missing and must be implemented in order to comply with the API.

Missing functionality

The two following configuration profiles are missing from the models:

• MobileDeviceConfigurationProfile
• OSXConfigurationProfile

Miscellaneous

Mobile device

{
    "general": {
        "id": 0,
        "name": "Corporate Wireless",
        "description": "string",
        "site": {
            "id": 0,
            "name": "None"
        },
        "category": {
            "id": 0,
            "name": "string",
            "priority": 0
        },
        "uuid": "55900BDC-347C-58B1-D249-F32244B11D30",
        "deployment_method": "Install Automatically",
        "redeploy_on_update": "Newly Assigned",
        "redeploy_Dayss_before_certificate_expires": 0,
        "payloads": "string"
    }
}

OSX

{
    "general": {
        "id": 12345,
        "name": "Corporate Wireless",
        "description": "string",
        "site": {
            "id": 0,
            "name": "None"
        },
        "category": {
            "id": 0,
            "name": "string",
            "priority": 0
        },
        "distribution_method": "Install Automatically",
        "user_removable": true,
        "level": "computer",
        "uuid": "88F8C1DB-D92A-4D10-95FB-CE7EDE82B93E",
        "redeploy_on_update": "Newly Assigned",
        "payloads": "string"
    }
}

Summary

Implement the functions that will return URLRequests for all requestable objects.

Implements #70 and #71.

Miscellaneous

Supports Objective-C meaning that each single object will implement the public version of each function but under the hood, the generic functions will be used. 😭

Supports CREATE, READ, UPDATE & DELETE methods.

Short description

To improve maintainability & cleanliness, the models needs to be reworked in a Protocol Oriented Programming way.

Implementation

Most of the classes inherits from BaseObject class or Identifiable protocol which is kind of messy. All the classes should adopt protocols instead of inheriting other classes.

New feature

Short description

Once the SessionManager is fully configured, it should be possible to retrieve URLRequests for all the models supported by JamfKit.

Missing functionnality

The SessionManager should be able to produce URLRequest that can be used by any user against the network communication framework of their choice.

Those requests should be available for the 4 methods currently supported by JSS:

• PUT
• GET
• POST
• DELETE

Implementation

TBD

Summary

Implements #64 by adding the basic element needed for configuring the URLRequest that will be returned / used later on by the framework.

Miscellaneous

Added SessionManager. Added base request creation. Added base errors.

New feature

Short description

Required by #63.

Implementation

Supply the users with a simple mean of configuring the Jamf host to target for JamfKit.

This will be used later to output URLRequest or to perform them directly.

Implements #33.

Splitted ComputerCommandGeneral from ComputerCommand. Added @objc on public properties. Refactored description properties to rely on class type instead of manual type.

Context

The PreciseDate class has been constructed to mimic the same behaviour as JSS payload when it comes to dates.

By acception a base key name, it allows the reconstruction of the 3 original keys for any date, like that:

{
    "example_date": "XXX",
    "example_date_epoch": 0,
    "example_date_utc": "XXX+0500"
}

If those keys were embedded in a single key it would have been much more simple to reconstruct the json before sending it to JSS.

An updated payload:

{
    "example_date": {
        "date": "XXX",
        "epoch": 0,
        "utc": "XXX+0500"
    }
}

Which in turn would improve the injection of each date in any JSON payload.

How it's currently done:

if let exampleDate = exampleDate {
    json.merge(exampleDate.toJSON()) { (_, new) in new }
}

Currently, this solution is problematic since the test coverage can't make it inside the block.

Issue

Find a better way of generating / injecting any date's JSON into another JSON payload.

Already gave it a try, pretty frustrating since there's a lot of unconventional JSS objects that are complex to translate into Codable objects.

Still worth a try, maybe some hybrid solution could be nice but it might be confusing to some.