Thanks for the expanded payloads and additional events, though I’d appreciate a clarification on the underlying platform strategy and consistency:
The previous event schema (
avi:activity:*) seemed to embrace the major industry trend towards “describing event data in a common way”, where a unified event envelope plus event type specific payload eases generic event routing and integration etc. (notably exemplified by AWS EventBridge and CNCF CloudEvents).
The new product specific events for Jira and Confluence now lack the envelope entirely (thus all contextual metadata), which requires additional code to retrofit a generic wrapper for consistent cross-product event handling, for no immediately apparent reason.
A more specific oddity seems to be the unification from
avi:confluence:created:comment, which in itself might more accurately reflect the backing content model, only to be an immediate DX head scratcher due to the simultaneous introduction of
The partially severe and never reconciled UX and DX inconsistencies between Jira and Confluence (and Bitbucket for that matter) for semantically similar concepts have been a major long-time pain for Atlassian users and developers alike, so I’ve been hopeful that the cross-product Forge platform would imply strategic improvements in this regard.
I realize that platform strategy and consistency as such would be topics for a separate thread, but could you expand a bit on what motivated the changes at hand?