You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an uncommon use case, but it's possible to have multiple endpoints with the same route if you have both REST & HTTP in use.
For example, if you're migrating from one to the other and run them in parallel:
Feature Request
This is an uncommon use case, but it's possible to have multiple endpoints with the same route if you have both REST & HTTP in use.
For example, if you're migrating from one to the other and run them in parallel:
Or if you have two fully distinct APIs that just happen to have matching paths in routes:
Currently Serverless Offline will fail with
AssertError: New route X conflicts with existing X
.Expected behavior
I'm not sure what the best way to handle this would be.
Some ways this could be handled:
Overloading the prefix type would make the documentation more confusing, though.
You could then run multiple instances of sls offline which ignore different sets of events.
The text was updated successfully, but these errors were encountered: