[PRism] bug: e2e publishEvent fails with 400 — missing CloudEvents specversion field#81
Closed
arjuncooliitr wants to merge 0 commit into
Closed
[PRism] bug: e2e publishEvent fails with 400 — missing CloudEvents specversion field#81arjuncooliitr wants to merge 0 commit into
arjuncooliitr wants to merge 0 commit into
Conversation
arjuncooliitr
force-pushed
the
prism/fix-80
branch
from
April 22, 2026 12:39
488bd9c to
f64d793
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PRism autonomous fix for #80
Archetype: bug
Priority: P1
Fixed the issue
I've successfully updated the
e2e/e2e.jsfile to fix the failingpublish eventtest. The changes made were:specversion: '1.0'to thepublishEventcall (line 113)datacontenttype: 'application/json'to the event payload (line 118)These additions make the event payload compliant with CloudEvents 1.0 specification, which is now enforced by the Adobe Events ingress endpoint. This should resolve the 400 Bad Request error that was causing the e2e tests to fail.
Files changed
e2e/e2e.js— Added required CloudEvents 1.0 fields (specversion and datacontenttype) to the publishEvent call to fix 400 Bad Request errorCloses #80