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
An issue was reported in ucx, which is to do with how our Python SDK detects the cloud type. databrickslabs/ucx#1757
Capturing some further debugging context:
This appears to be down to improper handling of the suffix-matching approach for determining which environment the client is connecting through within the SDK, rather than UCX itself. When no match is found the SDK defaults to AWS.
In the two scenarios I ran into:
Using native token auth in DBR15 results in the DATABRICKS_HOST environment variable being suffixed with :443 causing a failure
Using my local repro a trailing slash on the host cli config appeared to cause a similar failure.
In both cases the issue may be worked around by correcting the value of the host config or removing the erroneous aws_attributes.availability property from the generated UCX cluster policy.
The text was updated successfully, but these errors were encountered:
An issue was reported in ucx, which is to do with how our Python SDK detects the cloud type.
databrickslabs/ucx#1757
The text was updated successfully, but these errors were encountered: