Skip to content

Conversation

abdulmoemoh
Copy link

@abdulmoemoh abdulmoemoh commented Jul 15, 2025

Changes

Document additional custom properties for resource workspace_conf. These custom properties are currently supported, but not available in the current docs.

Tests

  • make test run locally
  • [ X] relevant change in docs/ folder
  • covered with integration tests in internal/acceptance
  • using Go SDK
  • using TF Plugin Framework
  • [ X] has entry in NEXT_CHANGELOG.md file

@abdulmoemoh abdulmoemoh requested review from a team as code owners July 15, 2025 10:56
@abdulmoemoh abdulmoemoh requested review from parthban-db and removed request for a team July 15, 2025 10:56
@abdulmoemoh abdulmoemoh changed the title Document additional custom properties for resource workspace_conf Document additional custom properties for resource workspace_conf Jul 15, 2025
Copy link

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/terraform

Inputs:

  • PR number: 4859
  • Commit SHA: 6a2eac01b1026ec0edb8f9e6a35dc48214ceae82

Checks will be approved automatically on success.

@abdulmoemoh abdulmoemoh changed the title Document additional custom properties for resource workspace_conf [Doc] Document additional custom properties for resource workspace_conf Jul 15, 2025
@nkvuong nkvuong requested a review from alexott July 16, 2025 03:35
@alexott
Copy link
Contributor

alexott commented Jul 16, 2025

@abdulmoemoh, Thank you for your PR, but these configurations aren't officially documented in the main Databricks docs, and they are subject to potential breaking changes; that's why they aren't documented in the Terraform docs. We had similar situation recently with one of the settings.

There is a work in progress on exposing such settings correctly, like this: https://docs.databricks.com/api/azure/workspace/enableexportnotebook/getenableexportnotebook. After that, existing settings could be decommissioned, but it's a decision of the corresponding development team.

Please reach your Databricks account team for further discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants