-
Notifications
You must be signed in to change notification settings - Fork 278
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
[Bug?] error calling MarshalHCL when trying to inspect schema #3397
Comments
I assume this is AWS Babelfish, right? There might be some differences between PostgreSQL and Babelfish-PG. Can you please share the SQL result you got? I will try to reproduce this. |
Yes it is, but I am using https://github.com/jonathanpotts/docker-babelfishpg to spin up Babelfish locally. After trying their example script I was actually able to extract the HCL using :
so the issue must be related to my other Thanks! |
Was able to narrow down the issue. HCL generation works in my
I will see if I can point exactly what index is causing the issue |
I'm on Windows and trying to inspect a
Postgres
schema using :.\atlas.exe schema inspect -u "postgres://babelfish_user:<password>@localhost:5432/babelfish_db?search_path=dbo&sslmode=disable"
and I get this error ⚠ :
Error: template: inspect:1:4: executing "inspect" at <$.MarshalHCL>: error calling MarshalHCL: must not call ListVal with empty slice
Also tried :
.\atlas.exe schema inspect -u "postgres://babelfish_user:<password>@localhost:5432/babelfish_db?sslmode=disable" -s dbo
and get the same error.
However, when I request SQL or JSON format using respectively :
.\atlas.exe schema inspect -u "postgres://babelfish_user:<password>@localhost:5432/babelfish_db?search_path=dbo&sslmode=disable" --format "{{ sql . }}" > script.sql
or
.\atlas.exe schema inspect -u "postgres://babelfish_user:<password>@localhost:5432/babelfish_db?search_path=dbo&sslmode=disable" --format "{{ json . }}" > script.json
it works fine! 🤔Any idea what could be wrong with the HCL generation? Thanks!
The text was updated successfully, but these errors were encountered: