Web API for Munki

[Gregory Neagle]

Inspired by this: http://ape-docs.groob.io

I’ve started work on what is planned to be a compatible API as part of MunkiWebAdmin2.

Available here: https://github.com/munki/mwa2/tree/api

manifests and pkgsinfo endpoints are supported. GET, POST, PUT, PATCH and DELETE are supported.

Some examples of interacting with the API (where the server is running at http://localhost:8080):

GET:

curl http://localhost:8080/api/manifests

curl "http://localhost:8080/api/manifests?api_fields=filename"

curl "http://localhost:8080/api/manifests?catalogs=testing"

curl "http://localhost:8080/api/manifests?catalogs=testing&api_fields=filename,catalogs"

curl "http://localhost:8080/api/manifests/site_default”

curl "http://localhost:8080/api/pkgsinfo?receipts=com.microsoft&api_fields=filename”

curl "http://localhost:8080/api/pkgsinfo/?installer_item_location=.mobileconfig&api_fields=filename,installer_item_location"

POST:

curl -H "Content-Type: application/json" -X POST --data '{ "filename": "fakepkg-1.0.plist", "name": "fakepkg", "catalogs": [“testing"],"display_name": "Example pkg"}' http://localhost:8080/api/pkgsinfo

PUT:

curl -H "Content-Type: application/json" -X PUT --data '{ "filename": "fakepkg-1.0.plist", "name": "fakepkg", "catalogs": [“production"], "display_name": "Example pkg"}' http://localhost:8080/api/pkgsinfo/fakepkg-1.0.plist

PATCH:

curl -H "Content-Type: application/json" -X PATCH --data '{ "version": "1.0" }' http://localhost:8080/api/pkgsinfo/fakepkg-1.0.plist

DELETE:

curl -X DELETE http://localhost:8080/api/pkgsinfo/fakepkg-1.0.plist

The API is rough and had ZERO authentication or authorization around it yet, so for the love of all that is holy do not point it at a live production repo.

-Greg

[Victor Vrantchan]

Thanks for creating the thread Greg, 

I'm updating the docs to reflect the latest changes. 

Here's the source of the current server - github.com/groob/ape

I'm hosting a temporary server at http://munki.groob.io/api/ with the repo accessible at http://munki.groob.io/repo

If anyone else is interested in an API and has suggestions for what the interface should look like or how the server should handle authentication/authorization, please reply. 

It'd be great to have a common spec/API interface even if the implementations are slightly different.