Moving ingress route to new module errors with duplicate http ingress <method>

[wesbillman]

When deploying on a customer repo, we ran into an issue where the deployment would error because of duplicate ingress routes.

I'm guessing this is because the route was already defined on module a and then moved to module b. The route might still exist in our ingress_routes table.

[wesbillman]

Found that the customer repo had an old deployment that had not been cleaned up. Removing that deployment resolved this issue so it seems like FTL was working as expected.

I also tested locally by moving a route from one module to another and it worked well.