[MGNLTEST-478] Solution to disable Receivers Created: 21/Dec/23  Updated: 05/Feb/24

Status: Selected
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Harshini Pola
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon PUBLISHING-318 Remove default receiver config from m... In Progress
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: core-TF-features-bugs-improvements
Work Started:

 Description   

info.magnolia.test.fixture.Receivers had been written for disabling/enabling receivers for tests - since self-tests rin against only one instance, the author instance.

The change in config done by the methods disable, enable cannot work anymore, since apparently publishing config has changed. On 6.2 it was configured via JCR.

Usages of this class should be removed for now.
Not yet sure whether we need to fix it.

Since 6.3 - receivers are configured via micro-profile.
This makes it a bit tricky to disable receivers on context of core-TF self-tests.

The location of a micor-profile yaml can be configured with a VM param.

-Dsmallrye.config.locations=/Users/sang.ngo/dev/mgnl-cloud/config/

This can be done locally, but it complicates local dev - at least partially.
For Jenkins - we would need to download such yaml-file and provide the location in the Jenkins-pipeline.
Doable - but, again, complicated.



 Comments   
Comment by Christoph Meier [ 22/Dec/23 ]

There may be more possibilities to provide micro-profile configs

Generated at Mon Feb 12 07:49:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.