API trigger on deployment to another environment
saul-data opened this issue · 2 comments
saul-data commented
- The API trigger url doesn't have the ID in url - it would not know where to route the trigger to
- To configure API triggers, user needs to click edit pipeline then configure API, similar to time schedule this should be direct
- Version conflicts between environments so if the same version of the trigger API pipeline is on one environment, it will conflict with another environment.
saul-data commented
onattech commented
Number 2 is fixed and pushed.