Two servers using the same schema, configured differently - only one works

[darvanen]

I have a composable schema which defines 20-odd schema extensions.
I have two endpoints/servers configured differently (different sets of extensions) via the UI with different machine names and different paths.

After I refresh the cache, whichever server I make a request of first takes over the endpoint of the other one and it stays that way until the next cache refresh.

This doesn't occur on local where most if not all caches are turned off.

[darvanen]

I think perhaps the operation result is missing a cache context for the server:

[darvanen]

Oh damn. schema_configuration is keyed by the schema id not the server id, and it's pulling the wrong server's schema before it instantiates the plugin.

[darvanen]

And that in turn appears to be because of some aggressive static caching in \GraphQL\Utils\SchemaExtender::extend

[darvanen]

Nope, it wasn't that, it was within the drupal module. This PR demonstrates where the schemas are being cached without respecting the server ID. Biggest problem I see here is the server ID isn't available to the plugin base in configuration.

#1224

[pfrenssen]

Created a corresponding drupal.org issue: https://www.drupal.org/project/graphql/issues/3491736

[klausi]

let's continue there!