0.8.3.rst 2.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344
  1. ==============
  2. salt-api 0.8.3
  3. ==============
  4. :program:`salt-api` 0.8.3 is a small release largely concerning changes and
  5. fixes to the :py:mod:`rest_cherrypy <salt.netapi.rest_cherrypy.app>` netapi
  6. module.
  7. This release will likely be the final salt-api release as a separate project.
  8. The Salt team has begun the process of merging this project directly in to the
  9. main Salt project. What this means for end users is only that there will be one
  10. fewer package to install. Salt itself will ship with the current ``netapi``
  11. modules and the API and configuration will remain otherwise unchanged.
  12. The reasoning behind merging the two projects is simply to lower the barrier to
  13. entry. Having a separate project was useful for experimentation and exploration
  14. but there was no technical reason for the separation -- salt-api uses the same
  15. flexible module system that Salt uses and those modules will simply be moved
  16. into Salt.
  17. Going forward, Salt will ship with the same REST interface that salt-api
  18. currently provides. This will have the side benefit of not having to coordinate
  19. incompatible Salt and salt-api releases.
  20. :py:mod:`rest_cherrypy <salt.netapi.rest_cherrypy.app>` changes
  21. ==================================================================
  22. An HTTP stream of Salt's event bus has been added. This stream conforms to the
  23. SSE (Server Sent Events) spec and is easily consumed via JavaScript clients.
  24. This HTTP stream allows a real-time window into a running Salt system. A client
  25. watching the stream can see as soon as individual minions return data for a
  26. job, authentication events, and any other events that go through the Salt
  27. master.
  28. A new configuration option to only allow access to whitelisted IP addresses. Of
  29. course, IP addresses can be easily spoofed so this feature should be thought of
  30. as a usability addition and not used for security purposes.
  31. An option to disable SSL has been added. Previously SSL could only be disabled
  32. while running the HTTP server with debugging options enabled. Now each item can
  33. be enabled or disabled independently of the other.
  34. In addition, there has been several bug fixes, packaging fixes, and minor code
  35. simplification.