fix/ remote relationships not loading #4485

[soorajshankar]

• https://github.com/hasura/graphql-engine/issues/4485

Description

Changelog

• [ ] CHANGELOG.md is updated with user-facing content relevant to this PR.

Affected components

• [ ] Server
• [x] Console
• [ ] CLI
• [ ] Docs
• [ ] Community Content
• [ ] Build System
• [ ] Tests
• [ ] Other (list it)

Related Issues

4485

Solution and Design

Found remote_relationships is not having data with configuration instead it has the required values with the key definition. Observed that this data is coming from the server in this shape, hence not so sure if this will be a permanent refactoring or a conditional one. In this situation made a handler that handles both the scenarios and makes sure that the UI renders error-free.

Steps to test and verify

1. Go to Console, open Remote schema.
2. Create a valid remote schema ( I used onegraph referring this)
3. Go to Hasura console
4. click on Data tab
5. Create a new data table.
6. click on Relationships tab.
7. Under Remote Relationships click on Add a new remote relationship button.
8. Choose the remote schema and create the remote schema relationship.
9. Click on the Save Button.

Current Behaviour

Remote schema relationship does not get created, it throws an error. as mentioned here #4485

Expected Behaviour

Remote schema relationship has to save successfully and it should be listed as shown below.

Limitations, known bugs & workarounds

If the key is permanently changed to definition then this extra check may not be required, also code pollution.

Server checklist

Catalog upgrade

Does this PR change Hasura Catalog version?

• [*] No
• [ ] Yes
  • [ ] Updated docs with SQL for downgrading the catalog

Metadata

Does this PR add a new Metadata feature?

• [*] No
• [ ] Yes
  • Does run_sql auto manages the new metadata through schema diffing?
  • [ ] Yes
  • [ ] Not required
  • Does run_sql auto manages the definitions of metadata on renaming?
  • [ ] Yes
  • [ ] Not required
  • Does export_metadata/replace_metadata supports the new metadata added?
  • [ ] Yes
  • [ ] Not required

GraphQL

• [*] No new GraphQL schema is generated
• [ ] New GraphQL schema is being generated:
  • [ ] New types and typenames are correlated

Breaking changes

• [*] No Breaking changes

• [ ] There are breaking changes:

  1. Metadata API

     Existing query types:

     • [ ] Modify args payload which is not backward compatible
     • [ ] Behavioural change of the API
     • [ ] Change in response JSON schema
     • [ ] Change in error code

  2. GraphQL API

     Schema Generation:

     • [ ] Change in any NamedType
     • [ ] Change in table field names

     Schema Resolve:-

     • [ ] Change in treatment of null value for any input fields

  3. Logging

     • [ ] Log JSON schema has changed
     • [ ] Log type names have changed

[soorajshankar]

@wawhal Please give your thoughts.

[soorajshankar]

I also put an error message as follows

Please let me know if this is not relevant. @wawhal