Version Information

Server Version:
hasura/graphql-engine:v2.48.1-ce.ubi

Environment

OSS

What is the current behaviour?

I created a remote schema with a space (Vault Engine) . After that, I reload the page. When I want to modify this remote schema, it is not found. I saw that the space is missing in the error.

"error": "remote schema with name \"VaultEngine\" doesn't exist",
"path": "$.args[0].args",
"code": "not-exists"

I deleted then created again with an underscore to replace the space and it works well

What is the expected behaviour?

Space should be accepted because it's a "friendly" name.

Any possible solutions/workarounds you're aware of?

Don't use space in remote schema name

Keywords

Remote schema