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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: