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
Describe the bug
Using the (edgedb.Client).WithConfig does not seem to actually do anything. All other client functionality seems to work as expected
Reproduction
conn, err=edgedb.CreateClient(context.Background(), edgedb.Options{
Host: host,
Port: edgedbPort,
SecretKey: edgedbSecretKey,
})
// The below does not seem to actually do its jobconn.WithConfig(map[string]interface{}{
"allow_user_specified_id": true,
})
Expected behavior
I expected this to achieve the same effect as if I ran the following EdgeQL: configure instance set allow_user_specified_id := true;
Versions (please complete the following information):
Additional context
I'm trying to do this on the setup of my API server in the context of docker-compose. The whole purpose of all of this is so I can run automated tests via GitHub Actions.
I ended up modifying my docker-compose.yml file to pass in an edgedb-bootstrap.yml as specified here so that I could at least make sure I was getting my config correct whether the Go library is working correctly or not.
The text was updated successfully, but these errors were encountered:
Describe the bug
Using the
(edgedb.Client).WithConfig
does not seem to actually do anything. All other client functionality seems to work as expectedReproduction
Expected behavior
I expected this to achieve the same effect as if I ran the following EdgeQL:
configure instance set allow_user_specified_id := true;
Versions (please complete the following information):
edgedb-go
version: 0.14.1-0.20230725211155-0d5d4814b9bdAdditional context
I'm trying to do this on the setup of my API server in the context of docker-compose. The whole purpose of all of this is so I can run automated tests via GitHub Actions.
I ended up modifying my
docker-compose.yml
file to pass in anedgedb-bootstrap.yml
as specified here so that I could at least make sure I was getting my config correct whether the Go library is working correctly or not.The text was updated successfully, but these errors were encountered: