-
Notifications
You must be signed in to change notification settings - Fork 183
Enable support for a single Profile to use both Account and Workspace endpoints #1232
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
base: main
Are you sure you want to change the base?
Conversation
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
|
|
||
|
|
||
| def test_account_operations(unified_config): | ||
| client = AccountClient(config=unified_config) |
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.
Won't this test be skipped because the unified config above is defined only for workspace?
_load_debug_env_if_runs_from_ide("workspace")
env_or_skip("CLOUD_ENV")
if "DATABRICKS_ACCOUNT_ID" in os.environ:
pytest.skip("Skipping workspace test on account level")
What changes are proposed in this pull request?
Enable support for a single Profile to use both Account and Workspace endpoints.
This is done by moving the header injection logic to the code generation, which is aware of which endpoints are workspace specific.
How is this tested?
Updated test.