The error indicates that AiGatewayConfig cannot be imported from databricks.sdk.service.serving after upgrading from version 16.3 to 16.4 LTD, signaling a breaking change or removal in the SDK.
Why This Happens
With minor version updates, Databricks SDK sometimes refactors, renames, or removes classes and methods—especially in non-LTS or major public releases. The absence of AiGatewayConfig suggests it was either:
-
Removed, renamed, or moved to a different module in 16.4 LTD.
-
Deprecated and replaced by another configuration object.
How to Resolve
1. Check SDK Release Notes
Look up the official Databricks SDK release notes or changelog for version 16.4 LTD for explicit details about the removal or migration of AiGatewayConfig.
2. Inspect the Module
Try the following in a Databricks cell or Python shell to see available names:
import databricks.sdk.service.serving as serving
dir(serving)
This helps identify if AiGatewayConfig is renamed, moved, or gone.
3. Update Your Imports
-
If AiGatewayConfig is moved, import it from its new location.
-
If it's replaced, update your code to use the new class/config.
4. Fallbacks
If you cannot find an alternative, examine the SDK documentation for examples of endpoint creation or AI Gateway configuration in version 16.4 LTD.
Quick Fix
-
Remove or replace AiGatewayConfig import: If your code doesn't depend directly on AI Gateway functionality, simply remove the import.
-
Find replacement class (if needed): Scan documentation for the correct configuration construct.
Example Update
from databricks.sdk.service.serving import (
ServedModelInput,
EndpointCoreConfigInput,
TrafficConfig,
Route,
# AiGatewayConfig, # Remove this if not present
AiGatewayInferenceTableConfig,
)
or, if you find a new location:
from databricks.sdk.service.ai_gateway import AiGatewayConfig
(Replace with actual path if changed.)
Next Steps
-
Check if you use AiGatewayConfig directly; if so, adapt to the new version.
-
For persistent issues, consult Databricks’ official migration guides.
Recommendation
Always validate imports and update code with each SDK upgrade, referencing release notes for deprecated or migrated features.