Break up each IFTTT applet into it's own repo

Question

Break up each IFTTT applet into it's own repo

Closed this issue 6 years ago · 1 comments

Answer 1 · 2019-03-11T23:05:45.000Z

After further review, this will be more work than we need. IFTTT is fairly strict about how an organization handles its API. It must be the same base route, and each trigger has a unique slug. We could achieve this in the future by using a reverse proxy, an API gateway (Apigee), or something like Istio if we go the microservices route.