Jesse Rosenberger

It is was very intentional that we haven't merely introduced a `--dev` flag to the Router thus far, so I'm going to convert this to a draft for now because...

Closing this in favor of https://github.com/apollographql/router/pull/1748, which definitely cargo-culted 👽 part of this implementation. Thanks! 😄

And we should consider where the configuration for this could live!

@atanuk Do you have any updates on this?

I'll close this since we haven't heard back from you, but happy to reopen if you're still experiencing the problem! Thanks for opening this originally!

This section specifically refers to bubbling: https://spec.graphql.org/October2021/#sel-HAPHRPTEBNBS1_I. One question comes to mind about if there are multiple steps of bubbling? We might want to try and emulate this behavior in...

@bnjjj Do you mind taking another look at this when you have a chance? Is this still relevant or something that we should talk about? (Feel free to close if...

To quote a bit from a non-GitHub convo: > In general, would be interested in finding a way for plugins to communicate with each other. E.g., a notification plugin might...

Thank you for opening this! I DO think this should be its own specific issue, but just want to note that this relates to #329. I'll also update that.

Since the default for [`STOPSIGNAL` is `SIGTERM`](https://docs.docker.com/engine/reference/builder/#stopsignal), does this mean that the router is _not_ terminating on merely `SIGTERM`?