Skip to content

[Feature] Enable the option to add comment when defining a new databricks_share #4802

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

rudolfsberzins
Copy link

Changes

Added the option for the user to define a comment when creating databricks_share which will be displayed in Databricks UI for defined share.

Additionally, made share.md documentation more consistent with Terraform style.

Tests

  • make test run locally
  • relevant change in docs/ folder
  • covered with integration tests in internal/acceptance
  • using Go SDK
  • using TF Plugin Framework

@rudolfsberzins rudolfsberzins requested review from a team as code owners June 18, 2025 09:18
@rudolfsberzins rudolfsberzins requested review from parthban-db and removed request for a team June 18, 2025 09:18
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: 4802
  • Commit SHA: 9742e91e619071502ecf23843e4db5ccc154242a

Checks will be approved automatically on success.

Comment on lines +233 to +241
if d.HasChange("comment") {
_, err = client.Shares.Update(ctx, sharing.UpdateShare{
Name: afterSi.Name,
Comment: afterSi.Comment,
})
if err != nil {
return err
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why can't we do this update together with Update call below or with update of owner?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants