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
I have a setup with only the postgres fdw and need to provide the credentials via json based config because the app/credentials-provider and the fdw run in 2 separate containers with no file exchange.
It always fails on some formatting issues. Is it possible to add some form of extended documentation of the json parsing from #318?
What is the correct hcl for json based credentials?
FdwError: failed to process options: failed to parse connection config for connection 'public': Extraneous data after value: Extra characters appear after
the JSON value.
Root value must be object: The root value in a JSON-based configuration must be either a JSON object or a JSON array of objects.
FdwError: failed to process options: failed to parse connection config for connection 'public': Missing attribute seperator comma: A comma must appear
between each property definition in an object.
Root value must be object: The root value in a JSON-based configuration must be either a JSON object or a JSON array of objects.
I have a setup with only the postgres fdw and need to provide the credentials via json based config because the app/credentials-provider and the fdw run in 2 separate containers with no file exchange.
It always fails on some formatting issues. Is it possible to add some form of extended documentation of the json parsing from #318?
What is the correct hcl for json based credentials?
hcl
Error is:
json
Error is:
How should the json object itself be formatted?
The text was updated successfully, but these errors were encountered: