-
Notifications
You must be signed in to change notification settings - Fork 86
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
Invalid Database Errors with Additional Keys When Connecting to Database via Gateway #302
Comments
Hi, I answered you by email but put the same answer here: Tell me how it goes. Cheers! |
Hello @loicknuchel, Thank you for your prompt response and the suggestions. Yes, I am using the Azimutt Docker Image tagged as ghcr.io/azimuttapp/azimutt:main. Regarding the Gateway version, I am running it with Node.js version 18.19.1, and the Gateway version is 0.1.7. I have tried running it both from the GitHub source code and using the command npx azimutt@latest gateway, and in both cases, the version is 0.1.7. Please let me know if there are any additional steps I should take or if there's a newer version of the Gateway I should be using. Thank you once again for your help! |
You were totally right, the |
Hello, I've tested the updated version 0.1.8 and I'm happy to report that everything is now working perfectly. Thank you for the swift response and resolution! |
Hello Azimutt Team,
I've encountered a couple of database validation errors when trying to connect my local database through the self-deployed Azimutt Gateway. Below are the errors:
These errors suggest that there are invalid additional keys in the entity attributes which are not expected by the Azimutt schema validation.
Details:
Questions:
I appreciate any help or insights you can provide as I am keen to resolve these issues and successfully connect my database through the Gateway.
Thank you for your support!
The text was updated successfully, but these errors were encountered: