0.1.1 (2024-03-27)¶
Breaking Changes¶
Users now required to explicitly have a role assigned within a namespace to manipulate HWMs as they could before. These changes enforce stricter access control and better management of user permissions within the system.
Add role model to Horizon, documentation available at Role Permissions. (#27, #31)
Restrict deletion of
Namespaceif there are anyhwmsrelated to it. (#25)
Features¶
Add
Namespace History. Now it is possible to view paginated history of actions for specific namespace. (#24)Add
owner_idfield toNamespacemodel to keep track of the owner of the namespace. (#26)Add support for managing
SUPERADMINroles. (#36)- Permissions Management:
Add new API endpoint
PATCH /namespace/:id/permissionsfor updating the permissions of users within a namespace.Add new API endpoint
GET /namespace/:id/permissionsfor fetching the permissions of users within a specific namespace.Extend the Python client library with methods
get_namespace_permissionsandupdate_namespace_permissionsto interact with the new API endpoints. (#29)
- High Water Marks (HWMs) Management:
Add new API endpoint
DELETE /hwm/for bulk deletion of High Water Marks (HWMs) by namespace_id and a list of hwm_ids.Extend the Python client library with the method
bulk_delete_hwmto interact with the new bulk delete HWM API endpoint. (#37)Add new API endpoint
POST /hwm/copyendpoint for copying HWMs between namespaces, with optional history copying.Extend the Python client library with the method
copy_hwmsto support the new HWM copy functionality. (#42)
Improvements¶
Fix documentation examples. Make documentation more user-friendly. (#20)