Yann Simon

Agree for the no-milestone. As we are already parsing the http, we could use the http request header (method, uri, version, headers) to pick up the right pool.

Yes or we have an additional component listening to K8S events, and using the REST API to synchronize.

@maniankara OK with that. We can also simply use docker images on nginx that always return 200

Yes, this sound interesting. From the documentation, I could not really understand how I can activate / deactivate certain contracts based on information from the HTTP request. From your comment,...

I don't know if you can work with external contributions, but I can check with my company if we can help you here. We could free some engineer time to...

> @yanns We do want external contributions, and we have started taking them in already. As you say though, this probably isn't the best ticket to start with. For context...

We've checked variants, and it seems to be too static for our use-cases. Maybe we need a new async method in the plugin, that takes the request and the supergraph...

> There is another approach that you could take: > > * Plugins now receive the schema at startup. This is to support schema driven extensions. > > * When...

Great news. We will try that.

I've implemented a technical prototype. To validate the query against the chosen schema, to avoid implementing again some code that is already in the router, I had to make some...