Repository navigation
Add direct-mode bundle support for AI Gateway model_provider_service - #6634
Merged
Merged
Conversation
alex-khakhlyuk
force-pushed
the
aigov-dabs-model-provider-service
branch
from
September 11, 2026 13:33
9a78c32 to
eb8fe3b
Compare
Collaborator
Integration test reportCommit: 13e7f9a
Top 1 slowest tests (at least 2 minutes):
|
| # rejects changing it via Update, so a local change must recreate. | ||
| - field: config.provider_type | ||
| reason: immutable | ||
| ignore_remote_changes: |
alex-khakhlyuk
force-pushed
the
aigov-dabs-model-provider-service
branch
from
September 14, 2026 12:51
eb8fe3b to
d1948b6
Compare
alex-khakhlyuk
force-pushed
the
aigov-dabs-model-provider-service
branch
2 times, most recently
from
September 14, 2026 17:55
5448793 to
1cd813f
Compare
alex-khakhlyuk
force-pushed
the
aigov-dabs-model-provider-service
branch
from
September 14, 2026 19:21
1cd813f to
e95c91a
Compare
janniklasrose
approved these changes
Sep 15, 2026
janniklasrose
left a comment
janniklasrose
left a comment
Member
There was a problem hiding this comment.
See nits in #6633, they apply here too
janniklasrose
added this pull request to stack #6683
September 15, 2026 10:47
alex-khakhlyuk
force-pushed
the
aigov-dabs-model-provider-service
branch
from
September 15, 2026 12:08
e95c91a to
ab540af
Compare
alex-khakhlyuk
force-pushed
the
aigov-dabs-model-provider-service
branch
from
September 15, 2026 13:34
ab540af to
e960e17
Compare
Third and last of the stacked split of #6410 (stacked on the mcp_service PR). Direct engine only; provider_type is immutable (recreate) and write-only provider secrets + server-computed fields are suppressed to avoid phantom drift. Co-authored-by: Isaac <no-reply@databricks.com>
Follow-up mirroring #6654 (model_services) and the mcp_services cleanup, now that #6618 enabled generating field behaviors from the response type. Added catalog.ModelProviderService to apitypes.yml, removed the hand-written recreate_on_changes (config.provider_type) and ignore_remote_changes (inference_table + write-only provider credentials) from resources.yml, and regenerated resources.generated.yml. The generator now derives all of these from the OpenAPI schema (and additionally picks up config.anthropic.relayed. plan_type as immutable); no suppression is lost. Co-authored-by: Isaac <no-reply@databricks.com>
…t_tag) Main upgraded databricks-sdk-go v0.177 -> v0.178, the GA-sync SDK that dropped `owner` (effective_owner only now), the request_tag rate-limit feature, and the anthropic relayed plan_type from the AI Gateway securable types. Adapted the model_provider_service resource to v0.178: removed the stale Owner field from modelProviderServiceBody, and regenerated schema/validation/refschema/pydabs. RATE_LIMIT_KEY_REQUEST_TAG is now absent from model_provider_services (and model_services / mcp_services), matching the v0.178 spec. Co-authored-by: Isaac <no-reply@databricks.com>
… configs/ layout Main #6679 split the monolithic resources.yml / resources.generated.yml into one file per resource under configs/. Recreate the model_provider_services rules in that layout: configs/model_provider_services.yml (provided_id_fields for the immutable parent + model_provider_service_id) and the regenerated configs/model_provider_services.generated.yml (provider_type recreate + the write-only provider-credential and inference_table suppressions, derived from catalog.ModelProviderService via apitypes.yml). No behavior change. Co-authored-by: Isaac <no-reply@databricks.com>
Addresses jannik's review nit on #6633 (deferred as a follow-up): the helper resolves the compound schemas/{catalog}.{schema} parent shared by the AI Gateway securables, so the more specific name makes the signature clear. Renames the definition and all three call sites (model_services, mcp_services, model_provider_services). No behavior change. Co-authored-by: Isaac <no-reply@databricks.com>
alex-khakhlyuk
force-pushed
the
aigov-dabs-model-provider-service
branch
from
September 15, 2026 13:36
e960e17 to
13e7f9a
Compare
janniklasrose
pushed a commit
that referenced
this pull request
Sep 15, 2026
…6634) Third and last of the stacked split of #6410 (stacked on the mcp_service PR). Direct engine only; provider_type is immutable (recreate) and write-only provider secrets + server-computed fields are suppressed to avoid phantom drift. ## Changes <!-- Brief summary of your changes that is easy to understand --> ## Why <!-- Why are these changes needed? Provide the context that the reviewer might be missing. For example, were there any decisions behind the change that are not reflected in the code itself? --> ## Tests <!-- How have you tested the changes? --> <!-- If your PR needs to be included in the release notes for next release, add a changelog fragment: create .nextchanges/<section>/<name>.md with a one-line description (e.g. .nextchanges/cli/quickstart.md). See .nextchanges/README.md. --> --------- Co-authored-by: Isaac <no-reply@databricks.com>
Collaborator
Integration test reportCommit: a1fee4b
312 interesting tests: 233 MISS, 68 FAIL, 7 KNOWN, 3 flaky, 1 SKIP
Top 50 slowest tests (at least 2 minutes):
|
deco-sdk-tagging Bot
added a commit
that referenced
this pull request
Sep 16, 2026
## Release v1.17.0 ### Notable Changes * Bump the direct deployment state version to 3. Clients older than v1.8.0 will reject bundles deployed with this release. ([#6713](#6713)) ### CLI * Add an `INVALID_REFRESH_TOKEN` error code to `databricks auth token --output json` failures. ([#6684](#6684)) * Add experimental `databricks auth docker configure` to configure Docker credential helper access for Databricks Artifact Registry. ([#6700](#6700)) * Add experimental `databricks auth docker token` to generate Docker credentials for Databricks Artifact Registry. ([#6699](#6699)) * `databricks environments setup-local` now reports the `E_PROVISION_CONFLICT` error code instead of the generic `E_PROVISION` when `uv sync` fails to resolve a dependency conflict. ([#6666](#6666)) * Preserve SSH sessions across temporary tunnel disconnects, with bounded replay and backpressure for large transfers. ([#6650](#6650)) * Allow OAuth U2M logins to override the CLI client ID with `--client-id`, profile `client_id`, or `DATABRICKS_CLIENT_ID`. ([#6594](#6594)) ### Bundles * direct: Store a dashboard's `serialized_dashboard` in state as a content hash instead of its full contents. ([#6105](#6105)) * direct: Fix pipelines recreation when the whole `ingestion_definition` block is added or removed. ([#6589](#6589)) * `bundle plan`, `deploy`, and `destroy` no longer report removing `permissions`, `grants`, or secret scope ACLs from a bundle as a deletion, since it leaves the resource untouched. ([#6647](#6647)) * `bundle plan` and `deploy` no longer list or count a resource that was already deleted remotely as a deletion, matching `bundle destroy`; applying still cleans up its stale state entry. ([#6675](#6675)) * Fix `bundle run` failing with `expected an int, found a string` when an unrelated resource references another resource that is not deployed. `bundle run` now resolves `${resources.*}` references only within the resource being run. ([#6690](#6690)) * Add grants support for the AI Gateway `model_service`, `mcp_service`, and `model_provider_service` resources (direct engine). ([#6635](#6635)) * Add bundle support for the AI Gateway `mcp_service` resource (direct engine). ([#6633](#6633)) * Add bundle support for the AI Gateway `model_provider_service` resource (direct engine). ([#6634](#6634)) * Add bundle support for the AI Gateway `model_service` resource (direct engine). ([#6525](#6525)) * Prevent resource drift on catalogs if `storage_root` contained a trailing slash in the URL. ([#6622](#6622)) * Fixed a "lineage mismatch in state files" error that could occur after destroying a bundle and redeploying it from another machine. `bundle destroy` now removes the local state file so no stale lineage is left behind, and prunes the state directories it leaves empty (such as `.internal/` and `sync-snapshots/`). ([#6210](#6210), [#6685](#6685)) * direct: `bundle plan` no longer reports a permanent update on a cluster that uses a cluster policy: when the cluster spec sets `policy_id`, a field present in the remote but absent from the bundle config is not treated as drift. ([#6531](#6531)) * `bundle deploy` on the direct engine now reports each resource as soon as it is deployed, instead of listing them all after the deployment finishes. A deploy that fails part way through now reports the resources it did apply. ([#6361](#6361)) * Direct-engine bundles no longer flag phantom drift on server-populated nested fields under reused config types (e.g. `external_locations` file-event-queue resource IDs, `database_instances` parent-instance refs, `apps` git credential ID). ([#6618](#6618)) * `databricks bundle generate app` now reproduces a git-backed app's `git_repository` and `git_source` configuration instead of emitting a workspace `source_code_path`, so generating from a Git-deployed app no longer silently converts it to workspace source. ([#6656](#6656)) * Improved configuration load time for bundles with many included files. ([#6195](#6195)) * `bundle destroy` no longer deletes triggered job runs, leaving them untouched on the backend. ([#6672](#6672)) * direct: resources.job\_runs: new lifecycle.triggers.on\_file\_change setting to restart the run when monitored files change. Can be set to a series of paths or globs. ([#6309](#6309)) * Bundle summary now shows a name for Postgres branches, endpoints, databases, and roles instead of a blank Name field. ([#6663](#6663)) * Added PyDABs (Python) support for cluster policies, dashboards, and Genie spaces. ([#6585](#6585)) * CLI commands no longer imply that a resource whose type has no workspace URL is merely not deployed yet. ([#6583](#6583)) * Capture the implicit dependency a vector search index has on a catalog or schema defined in the same bundle, so the catalog and schema are deployed first. ([#6655](#6655)) ### Dependency Updates * Bump dependencies with known vulnerabilities. ([#6695](#6695)) * Bump `github.com/databricks/databricks-sdk-go` from v0.177.0 to v0.178.0. ([#6673](#6673)) * Bump Terraform provider from v1.131.0 to v1.132.0. ([#6671](#6671))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Third and last of the stacked split of #6410 (stacked on the mcp_service PR). Direct engine only; provider_type is immutable (recreate) and write-only provider secrets + server-computed fields are suppressed to avoid phantom drift.
Changes
Why
Tests