[MGNLHOOK-204] Same webhook definition in two different light modules Created: 02/Sep/22  Updated: 08/Sep/22  Resolved: 08/Sep/22

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

Type: Bug Priority: Neutral
Reporter: Javier Benito Assignee: Unassigned
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
documentation
to be documented by MGNLHOOK-214 DOC: Same webhook definition in two d... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLHOOK-205 Implement fix Technical task Completed Javier Benito  
MGNLHOOK-206 Review Technical task Completed Jaroslav Simak  
MGNLHOOK-207 piQA Technical task Completed Jaroslav Simak  
MGNLHOOK-208 QA Technical task Completed Chuong Doan Huy  
MGNLHOOK-209 Port to 2.0.0 Technical task Completed Javier Benito  
MGNLHOOK-211 Review port to 2.0.0 Technical task Completed Chuong Doan Huy  
MGNLHOOK-212 piQA ported version Technical task Completed Chuong Doan Huy  
MGNLHOOK-213 QA ported version Technical task Completed Chuong Doan Huy  
Team: DeveloperX
Date of First Response:
Epic Link: Webhooks Maintenance (Phase 1)
Sprint: DevX 18
Story Points: 5

 Description   

Check if having the same webhook definition file in two different light-modules, affects webhooks activation in any way.

If it does, fix the problem, for example, prepending the light-module name to the generated rest client/webhook definitions.

This is what can be causing the problem stated in the linked HELPDESK issue.


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