Uploaded image for project: 'Magnolia Webhooks'
  1. Magnolia Webhooks
  2. MGNLHOOK-309

Make REST client environment aware on SaaS

    XMLWordPrintable

Details

    • Story
    • Resolution: Fixed
    • Neutral
    • 2.0.0
    • None
    • None

    Description

      Description

      REST client environment awareness on SaaS at this moment doesn't work well, it only manages properly one environment at a time.

      Steps to reproduce

      • Create a webhook definition file on main environment, named webhook1 and having webhook1 as name inside the yaml file.
      • Push the file to git main branch.
      • Create the same file, with different URL for the request, but in environment/branch env/test.
      • Push the file to git env/test branch.

      Current behaviour

      When the file is pushed to env/test, it overrides the URL on the automatically created Rest Client (it can be checked on Definitions app on both environments, the share the same configuration).

      Expected behaviour

      Each environment must have its own Rest Client definition, even if the names are the same, so Rest Client definitions must be Environment Bounded.

      Developer notes

      We'll need to check if the problem is on Rest Client (how it manages definitions coming from different environments) or in Webhooks module (how it automatically creates/removes Rest Clients).

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            There are no Sub-Tasks for this issue.

            Activity

              People

                dai.ha Dai Ha
                jbenito Javier Benito
                DeveloperX
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: