On Sat, 2016-10-22 at 19:03 +0000, Kevin Long wrote: > Could anyone knowledgeable be so kind as to inform me of the current status of 389's REST API? > > 1. Is it functional, stable ? > 2. What can be done with it currently? > 3. To what extent does the 389 server need to be configured before the REST API can be utilized? Hi, It's partially functional, but not stable. You can use it to search and change some values, but not a lot. You need to do a lot of work to make the rest api currently usable. I would say unless you are willing to get deep into some python 3 code, on Fedora 24 or higher, you may not want to use it yet. If you are keen, I'm happy to get some docs updated so you can give it a go. I'm glad you're interested in it though, and pay attention for more updates in this space. If you want to follow more, have a look at the 389-devel mailing list, and look at our trac instance. A lot of the work at the moment is laying the foundations for lib389 (our python library) so that the rest api (rest389) is a thin layer on top. For the moment you may want to look at what we are doing with the new command tools, as this will have similar capabilities to rest in the future. Thanks, -- Sincerely, William Brown Software Engineer Red Hat, Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
