...
Any ruleset wishing to create the subscription signals the CloudOS to do so by raising the the
system:subscribe subscribe
event. This is most often done in a rule postlude as shown in the following example:Code Block | ||||
---|---|---|---|---|
| ||||
fired { raise cloudos event subscribe with channelName = "Coworkers Bob+Ted" and namespace = "MyFriends" and relationship = "friend-friend" and targetChannel = "3f15b820-fa7f-012f-4c6e-00163ebccdcd" and _api = "sky"; } |
The CloudOS service raises the cloudos:subscriptionRequestAdded
to the target cloud:
Domain | cloudos |
---|---|
Type | subscriptionRequestAdded |
Attributes | targetChannel, backChannel, namespace, relationship, channelName |
The backChannel
attribute contains an ECI for the originating cloud that the CloudOS service has created and will pass to the target cloud.
...
To approve the subscription request a ruleset in the the target cloud raises the cloudos:subscriptionRequestApproved
event to signal the CloudOS service that the subscription is approved:
Domain | cloudos |
---|---|
Type | subscriptionRequestApproved |
Attributes | eventChannel |
For example, the following postlude would raise the cloudos:subscriptionRequestApproved
event:
...