Page Comparison

...

For example: pipeforce.event.workflow.# matches all workflow event messages while pipeforce.event.workflow.*.my.app matches only workflow event messages inside the app my.app.

pipeforce.event.app

This topic group forwards all important events related to app management.

.install.finished

This event message is send after an app was successfully installed.

The full structure of the event message routing key is like this:

pipeforce.event.app.install.finished

.uninstall.finished

This event message is send after an app was successfully uninstalled.

The full structure of the event message routing key is like this:

pipeforce.event.app.uninstall.finished

pipeforce.event.iam

This topic group forwards all important events happening inside IAM.

...

Every property topic key can additionally contain dynamic variables which will be replaced at runtime such as:

{pathappName} = Will be replaced by the app name the property is stored inside (example: io.pipeforce.myapp).

{path} = The path of the related property whereas slashes in path of property will become dots. Dots and special chars in origin path will be replaced by underscores. Everything in path is lower-cased.

...

pipeforce.event.property.updated.{path}

.comment.created

This event message is send after a comment was added to a property.

The full structure of the event message routing key is like this:

pipeforce.event.property.comment.created.{appName}

.comment.updated

This event message is send after a comment was updated to a property.

The full structure of the event message routing key is like this:

pipeforce.event.property.comment.updated.{appName}

pipeforce.event.log

This topic group forwards all important log events of severity level WARN or higher.

...