There are a few ways requests hitting the App Engine servers get routed to your application's modules. Namely, URL routing <https://cloud.google.com/appengine/docs/python/how-requests-are-routed#routing_via_url> and via dispatch rules <https://cloud.google.com/appengine/docs/python/config/dispatchref>. If there is dispatch.yaml in your `gcloud app deploy` command, the rules contained within will be applied before URL routing.
- What dispatch rules do you have in your dispatch.yaml? - A request to what URL was incorrectly routed to your default module? - What specific rules are expected to route requests to module B? On Monday, July 4, 2016 at 1:54:13 PM UTC-4, Mayank Bhagya wrote: > > We have a jenkins push-to-deploy setup that uses gcloud to deploy an > appengine application. > > After the deployment, suddenly all requests going to a module B start > going to a module A (default module)!? > > How is that possible? > Why is the dispatcher screwed up after a 'gcloud preview app deploy'. > This has hurt many of our users today. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/91f27847-80b2-4f1a-9007-023d4135cfb3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
