-
Notifications
You must be signed in to change notification settings - Fork 25
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
Always respect EDGEDB_CLOUD_PROFILE when connecting to cloud #235
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. But we should probably also have a shared test case to cover this issue.
fwiw you can revert edgedb/shared-client-testcases#22 to get at least one test case for |
Cloud instances, unlike local instances, do not represent local configuration, so `EDGEDB_CLOUD_PROFILE` should always be respected when connecting to such instances regardless of how compound connection options have been specified.
This reverts commit 5f2453c. `EDGEDB_CLOUD_PROFILE` is special. See edgedb/edgedb-rust#235.
|
This reverts commit 5f2453c. `EDGEDB_CLOUD_PROFILE` is special. See edgedb/edgedb-rust#235.
Cloud instances, unlike local instances, do not represent local
configuration, so
EDGEDB_CLOUD_PROFILE
should always be respectedwhen connecting to such instances regardless of how compound
connection options have been specified.