Description

reload_remote_schema does not work on remote schemas which are inconsistent (i.e. they were not available on startup). Considering prior discussions (see: #3792 ), this is actually a bug because even reload_metadata does not refresh remote schemas. There is no way to resolve an inconsistent remote schema without restarting Hasura.

Repro:

1. Run hasura (any version > 1.0.0)
2. Add a remote schema. E.g. this: https://github.com/hasura/preview-remote-joins/tree/master/graphql-services/weather
3. Stop hasura and remote schema
4. Start hasura -> remote schema becomes inconsistent
5. curl -d'{"type": "reload_remote_schema", "args":-schema" }}' localhost:8080/v1/query -> throws an error: {"path":"$.args","error":"remote schema with name \"my-remote-schema\" does not exist","code":"not-exists"}

Note for versions prior to v1.1.0: reload_metadata API would actually fetch inconsistent remote schemas and hence would resolve the inconsistency (although it wouldn't refresh consistent remote schemas).