Version History
This section describes changes made in subsequent releases and the new features in this API:
| Release | Enhancements | API Version |
|---|---|---|
| 2026.2 and Patch in API 2026.1 | To ensure consistency with the backend, we introduced the following endpoints: - GET /api/v1/system/getEventDetails - allows the API client to obtain system IDs and event IDs last check-in information for the specified system name. - GET /api/v1/systemgroup/listSystems - retrieves a list of systems associated with the specified system group. The user must have access to that system group. - POST /api/v1/system/custominfo/createKey - creates a new system key. - POST /api/v1/system/custominfo/deleteKey - deletes an existing system key and all system values for the key. - POST /api/v1/system/custominfo/updateKey - updates the description of the system key. - GET /api/v1/system/custominfo/listAllKeys - retrieves the list of the system information keys defined for the users organization. | v1 |
| 2026.2 and Patch in API 2026.1 | To ensure consistency with the backend, we introduced the following endpoints: - GET /api/v1/system/getDmi - retrieves the DMI information of a system. - GET /api/v1/system/getNetworkDevices - returns the network devices for the given server. | v1 |
| 2026.2 | To ensure consistency with the backend, we introduced the following endpoints: - DELETE /api/v1/queues/{vhost}/{name} - enables the API client to delete a RabbitMQ queue. - DELETE /api/v1/queues/{vhost}/{name}/contents - enables the API client to delete the contents of a RabbitMQ queue. | v1 |
| Patch in API 2024.2-SP5 | To return a list of systems that have completed a specific action, we introduced a new endpoint: - GET /api/v1/actions/listCompletedSystems - allows the API client to obtain a list of the completed system IDs and last check-in information for the given system action IDs. | v1 |
| 2024.2-SP5 | To return a list of systems that have failed a specific action, we introduced a new endpoint: - GET /api/v1/actions/listFailedSystems - allows the API client to obtain a list of the failed system IDs and last check-in information for the given system action IDs. | v1 |
| 2024.2-SP5 | To enhance mutual TLS Authentication process, we automated a process of user handling in RabbitMQ and exposed the following endpoints: - PUT /api/v1/users/{name} - enables the API client to create a RabbitMQ individual user. - DELETE /api/v1/users/bulk-delete - bulk deletes a list of RabbitMQ users. - PUT /api/v1/permissions/{vhost}/{user} - assigns user to virtual host and defines user permissions. | v1 |
| 2023.2 | To enable communication and exchange of necessary configuration data in the deployment process we have released the Deployment API. It supports user with setting up Edge deployment and helps to connect system to target Uyuni server. In our Deployment API we defined a set of endpoints allowing to communicate with Uyuni API: - GET /api/v1/healthCheck - enables to check health of the backend system. - POST /api/v1/saltkeys/search - returns a list of salt keys with the following statuses: accepted, pending, rejected, denied. - POST /api/v1/saltkeys/accept - enables to accept the connection key. - POST /api/v1/saltkeys/delete - enables to deregister a salt key. - GET /api/v1/system/getId - enables to obtain system IDs and last check in information for the given system. - POST /api/v1/system/deleteSystem - enables to delete a system. - POST /api/v1/system/scheduleApplyHighstate - enables to apply highstate settings to the registered system. - POST /api/v1/system/scheduleApplyStates - on successfully registering the system in Uyuni, user can assign states to the given system. - GET /api/v1/actions/{id} - returns details of an action based on an action identifier. | v1 |