Add AI Gateway securables to databricks_grant/databricks_grants - #5941
Open
khakhlyuk wants to merge 1 commit into
Open
Add AI Gateway securables to databricks_grant/databricks_grants#5941khakhlyuk wants to merge 1 commit into
khakhlyuk wants to merge 1 commit into
Conversation
The databricks_ai_gateway_model_service, _mcp_service, and _model_provider_service resources shipped in v1.124.0 (auto-generated via the plugin framework), but their UC permissions could not be managed in Terraform because the grants resources' SecurableMapping was never extended. Add model_service, mcp_service, and model_provider_service to permissions.Mappings, which generically exposes them as fields on both databricks_grant and databricks_grants (schema fields, ID parsing, and AtLeastOneOf are all driven off the map). Privileges pass through unchanged, so EXECUTE / MANAGE / ALL_PRIVILEGES work immediately. Securable-type strings verified against the Grants API. Update the no-securable error fixture for the three new fields and document the new securables in the grant/grants resource docs.
khakhlyuk
force-pushed
the
add-ai-gateway-securables-to-grants
branch
from
August 11, 2026 18:48
362eec6 to
ec960dc
Compare
Contributor
Unit testsIf this PR is from a fork, the If this PR changes Actions -> Warm Go Cache -> Run workflow -> pr_number = 5941 Re-run the failed check once the cache warming completes. Integration testsIntegration tests don't run automatically for external contributors; an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
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
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.
The databricks_ai_gateway_model_service, _mcp_service, and _model_provider_service resources shipped in v1.124.0 (auto-generated via the plugin framework), but their UC permissions could not be managed in Terraform because the grants resources' SecurableMapping was never extended.
Add model_service, mcp_service, and model_provider_service to permissions.Mappings, which generically exposes them as fields on both databricks_grant and databricks_grants (schema fields, ID parsing, and AtLeastOneOf are all driven off the map). Privileges pass through unchanged, so EXECUTE / MANAGE / ALL_PRIVILEGES work immediately.
Securable-type strings verified against the Grants API. Update the no-securable error fixture for the three new fields and document the new securables in the grant/grants resource docs.
Changes
Tests
make testrun locallydocs/folderinternal/acceptanceNEXT_CHANGELOG.mdfile