Introduction
Event notifications
Aruna includes an event notification service which can be used to subscribe to specific resources including their subresources. This means that the created event notification consumer can be used to fetch notifications regarding all actions which affected the resources in the scope of the consumer.
The event notification system is based on the integration of the cloud native, open source messaging technology NATS.io
These notifications have a shelf life, so they are not persistent forever. The exact concept of how many notifications are retained over what period of time is not yet final.
Create event notification consumer
API examples of how to create an event notification consumer.
Required permissions
This request requires at least READ permissions on all resources in the scope of the consumer.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
|
Fetch messages via batch
API examples of how to fetch an event notification message batch.
Required permissions
This request requires at least READ permissions on all resources in the scope of the consumer.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
|
1 2 3 4 5 6 7 8 9 10 11 |
|
Fetch messages via stream
API examples of how to fetch event notification messages via stream.
Required permissions
This request requires at least READ permissions on all resources in the scope of the consumer.
1 2 3 4 5 6 7 8 9 10 11 12 13 |
|
1 2 3 4 5 6 7 8 9 10 |
|
Acknowledge messages
Event notification messages have to be acknowledged in order that they won't be delivered again to the consumer after a set period of time.
Required permissions
As the complete Reply
(including a secure HMAC) is also delivered with the message individually for the consumer there are no special permissions required.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
|
Delete event notification consumer
API examples of how to delete an event notification consumer.
Required permissions
This request requires at least WRITE permissions.
1 2 3 4 5 6 7 8 9 10 11 12 13 |
|
1 2 3 4 5 6 7 8 9 10 |
|
Personal notifications
Some notifications are not based on actions in Aruna that affected specific resources but are addressed directly to a specific user. These notifications have to be persistent and therefore are retained separately from the event notification system until explicitly acknowledged.
Examples for personal notifications would be permission changes on resources or access requests on resources from other users.
Get personal notifications
API examples of how to fetch persistent personal notifications.
Required permissions
This request only requires a personal token which authenticates and provides the user id.
1 2 3 4 5 6 7 8 9 10 11 |
|
1 2 3 4 5 6 7 8 |
|
Acknowledge personal notifications
API examples of how to acknowledge persistent personal notifications.
Required permissions
This request only requires a personal token which authenticates the user.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
|