Uploaded image for project: 'Magnolia Test Framework'
  1. Magnolia Test Framework
  2. MGNLTEST-337

Implement S3-driven-definition-update-service (S3DDU)

    XMLWordPrintable

Details

    • Task
    • Resolution: Duplicate
    • Neutral
    • None
    • None
    • None

    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?

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              roberto.gomez Roberto Gomez
              Foundation
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoR