[MGNLHOOK-141] Integrate webhooks with Norsu Created: 13/Jun/22  Updated: 05/Oct/22  Resolved: 05/Oct/22

Status: Closed
Project: Magnolia Webhooks
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0.0

Type: Story Priority: Neutral
Reporter: Jaroslav Simak Assignee: Dai Ha
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLHOOK-240 Create norsu webhook action to be use... Backlog
relates to MGNLHOOK-239 Complete the norsu payload with nodet... Closed
dependency
depends upon MGNLHOOK-195 Make webhooks-events JCR agnostic Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLHOOK-233 Implement Sub-task Completed Dai Ha  
MGNLHOOK-235 Review Sub-task Completed Javier Benito  
MGNLHOOK-236 piQA Sub-task Completed Javier Benito  
MGNLHOOK-237 QA Sub-task Completed Chuong Doan Huy  
Team: DeveloperX
Documentation update required:
Yes
Date of First Response:
Epic Link: Webhook on SaaS
Sprint: DevX 20
Story Points: 5

 Description   

Take into account two things:

  • JCR
  • Way how (un)publication works in Norsu


 Comments   
Comment by Javier Benito [ 26/Aug/22 ]

It sounds good to me, instead of having a Node inside the event that is sent to the queue, have a different object less JCR-related, or maybe just the properties that we are using right now.

As far as I know, the node inside the event is not used nor propagated.

We should also change probably the way it's retrieved, now it's done using getJCRNode which is available on a RuleBasedCommand.

Comment by Jaroslav Simak [ 26/Aug/22 ]

Removal the JCR API will be handled by MGNLHOOK-195 in the next sprint.

Comment by Javier Benito [ 26/Aug/22 ]

Perfect, should we add it to MGNLHOOK-10 epic to keep track of it? 

Comment by Jaroslav Simak [ 26/Aug/22 ]

Yes please

Comment by Javier Benito [ 26/Aug/22 ]

Done

Generated at Mon Feb 12 10:01:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.