-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
DevX 28
-
5
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).
- relates to
-
MGNLHOOK-307 Random problem reading environments on module startup
- Closed
-
MGNLHOOK-308 Use new api to register custom rest client definition from webhooks
- Closed