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
Server Version:
CLI Version (for CLI related issue): 2.37.0
Environment
local
What is the current behaviour?
When i restart the hasura container using the hasura/graphql-engine:v2.37.0.cli-migrations-v3, custom functions that i have tracked before and show in metadata files (see screenshots) are untracked and i must manually add them back by clicking "TRACK"
What is the expected behaviour?
It's expected that tracked custom functions would pull from metadata files
How to reproduce the issue?
idk - sorry
Screenshots or Screencast
Please provide any traces or logs that could help here.
no errors. functions are just untracked
Any possible solutions/workarounds you're aware of?
i am going to try calling the metadata API to reenable on startup
Keywords
Custom Functions, Untracked
The text was updated successfully, but these errors were encountered:
Version Information
Server Version:
CLI Version (for CLI related issue): 2.37.0
Environment
local
What is the current behaviour?
When i restart the hasura container using the hasura/graphql-engine:v2.37.0.cli-migrations-v3, custom functions that i have tracked before and show in metadata files (see screenshots) are untracked and i must manually add them back by clicking "TRACK"
What is the expected behaviour?
It's expected that tracked custom functions would pull from metadata files
How to reproduce the issue?
idk - sorry
Screenshots or Screencast
Please provide any traces or logs that could help here.
no errors. functions are just untracked
Any possible solutions/workarounds you're aware of?
i am going to try calling the metadata API to reenable on startup
Keywords
Custom Functions, Untracked
The text was updated successfully, but these errors were encountered: