v1.0.0-rc.2

Small update in preparation for 1.0.0, full changelog see: #54

v1.0.0-rc.1

Set of changes needed for V1.0.0, full changelog see: #53

v0.5.0-beta.10

Preparation for 0.5.0: Small release that only adds annotations for unfinished services and comments for the current Status of each service. STABLE rpcs will not change before v1.0.0 and will go through an extended deprecation period if they will be changed.

v0.5.0

Release 0.5.0: This release contains many bugfixes and changes in existing APIs and is a first major step towards the 1.0.0 release. Serviceaccount Service and Info services as well as Notification services are laid out but still need proper testing and validation. All core resources (Object, Objectgroup, Collection, Project) should now contain stable methods (see Status comment). These STABLE methods are guaranteed to persist till at least v1.0.0 and will not be changed without an extended deprecation warning. ALPHA and BETA rpcs might still change on a short timeframe. If you find any issue please report them in the appropiate repo (or as fallback in the ArunaStorage/ArunaServer repo).

v0.5.0-beta.9

This release contains one small change to the hierarchy service (removal of project_id) and the addition of the new service account service. A full changelog can be found in the associated PR #47

v0.5.0-beta.8

Added full notification support, small changes to ObjectGroups / Collections. Full list of changes can be found here: #44

v0.5.0-beta.7

This is a small update to the API with one breaking change. It removes the with_history boolean flag from get_objects. It also changes the get_objects REST subpath to ../objects from ../object

v0.5.0-beta.6

This is a small update to the API with one breaking change. It removes the with_history boolean flag from get_objects. It also changes the get_objects REST subpath to ../objects from ../object

v0.5.0-beta.5

Added DeleteObjects method to delete multiple objects at once.

v0.5.0-beta.4

Pre-release 0.5.0-beta.4 includes additions to the internal API structures needed for the notification service. It introduces a new internal API service that is used to create check and authenticate notification streams and stream groups.