David Barroso
David Barroso
Hi, based on the logs you shared the service started correctly. The error you are pointing out in hasura is benign, it is simply hasura-storage reapplying metadata in case something...
Sorry, we missed this PR somehow. I don't think this is a problem in hasura-auth. From the looks of it, it looks like: 1. You have a project that references...
Closing this PR as we don't have plans to merge it, this is a deployment issue. @xmlking refer to my previous comment. This is an ordering issue in your deployment...
Closing in favor of #493 Thanks!
You are right, that documentation needs to be updated to mention that only `.` and `[]` are supported, not the full spec.
if you need to select only one in particular for some reason you can try adding a computed field and using that instead.
No progress yet as this hasn't been a priority. If this is a must for you don't hesitate to reach out to us via discord/email so we can discuss it....
Ok, I could reproduce with an empty `AUTH_API_PREFIX`. If you have a solution that doesn't involve changing current behavior a PR is more than welcomed. Otherwise we will try to...
@jonlambert let us know if you are interested in contributing this feature
I can confirm the same behavior. On a newly created instance it fails, after stop/start it works fine.