Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Native query and logical model added using the hasura console (graphql) is not added to metata on disk #10217

Open
andoks opened this issue Apr 25, 2024 · 1 comment
Labels
k/bug Something isn't working

Comments

@andoks
Copy link
Contributor

andoks commented Apr 25, 2024

Version Information

Server Version: v2.35.3 (hasura/graphql-engine:v2.35.3.cli-migrations-v2@sha256:bca701bfde562be1de16ea8d34295b5bd17494204151f606fa6656b80baa5ce4)
CLI Version (for CLI related issue): v2.35.3

Environment

OSS

What is the current behaviour?

When creating a native query and its required logical model using hasura console, neither the native query nor the logical model are added to the hasura configuration files (metadata).

Note that the native query and logical model does show up when I try to download the metadata from settings in hasura console. Maybe this is related to still using config v2 instead of v3?

What is the expected behaviour?

When creating native query and logical model using the hasura console, the native query and logical model are added to the metadata files

How to reproduce the issue?

  1. Using the above mentioned version of the cli and server, create a native query, e.g server_time with the query select now() at time zone 'utc' AS "current_time_utc";, also add the required logical model
  2. After saving both native query and model, go test it in the API tab, observe that it works
  3. Observe that none of the metadata files have been updated

Screenshots or Screencast

Please provide any traces or logs that could help here.

Any possible solutions/workarounds you're aware of?

No

Keywords

native query, native queries, logical model, cli, console

@andoks andoks added the k/bug Something isn't working label Apr 25, 2024
@andoks
Copy link
Contributor Author

andoks commented Apr 30, 2024

After testing, I can confirm that this only happens if using v2 of the configuration format. It works ok with v3 config format

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant