[MGNLTEST-337] Implement S3-driven-definition-update-service (S3DDU) Created: 03/Nov/22  Updated: 03/Nov/22  Resolved: 03/Nov/22

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

Type: Task Priority: Neutral
Reporter: Roberto Gomez Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: subscription-life-cycle-support-by-test-fwk
Team: Foundation

 Description   

To think about:

 DevX has mostly legit scenarios for using a real git repo with different sequence of events, including real pushes/branch creation/deletion.
Most other teams do not have requirements (at the moment) for light-module fixtures, changing throughout a scenario. So we may not need a mock s3 ingestion shortcut quite yet (but add some definitions to a constant location instead).

at the moment, that location would be in hello-saas repo (the one which is linked/provisioned with each test sub).
A proposal: not to pollute hello-saas' master branch (used for tutorial & onboarding purposes), we could maintain a "test" branch, there with additional light-modules & definitions for tests. From time to time, we would rebase this branch onto master, as needed.

 
We know that git push functionality is needed. The thing do we need an S3 push as well?



 Comments   
Comment by Roberto Gomez [ 03/Nov/22 ]

Duplicated See MGNLTEST-330

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