Skip to content
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

[DOC] Issue with databricks_workspace_binding argument securable_type #4307

Closed
Lorenzvanijperen opened this issue Dec 10, 2024 · 4 comments
Closed
Labels
docs add explicit documentation about corner case

Comments

@Lorenzvanijperen
Copy link

Affected Resource(s)

https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/workspace_binding#securable_type-1

Expected Details

Docs shows:

securable_type - Type of securable. Can be catalog, external-location or storage-credential. Default to catalog. Change forces creation of a new resource.

Code shows:
Error: expected securable_type to be one of ["catalog" "external_location" "storage_credential"], got external-location

List of things to potentially add/remove

This is a list of things to manipulate in the docs:

  • storage-credential --> storage_credential
  • external-location --> external_location
@Lorenzvanijperen Lorenzvanijperen added the docs add explicit documentation about corner case label Dec 10, 2024
@alexott
Copy link
Contributor

alexott commented Dec 10, 2024

addressed in #4293

@Farhan047
Copy link

addressed in #4293

I believe this should also resolve the below error :

 Error: expected securable_type to be one of ["catalog" "external_location" "storage_credential"], got credential

The API supports it, but the current version of the provider doesn't, this PR #4293 should help address that.

FYI, I am trying to create a service credential with a workspace binding, for a Managed Identity (azurerm_databricks_access_connector) as a Secrets User on an Azure Key Vault.

Question, do we know when you are planning to merge this PR ? And a timeline on the release this change will be part of ?

@alexott
Copy link
Contributor

alexott commented Dec 17, 2024

Will be resolved by merging #4328

@Farhan047 release with the fix will be tomorrow (most probably)

@alexott alexott closed this as completed Dec 17, 2024
@Farhan047
Copy link

Will be resolved by merging #4328

@Farhan047 release with the fix will be tomorrow (most probably)

Thanks @alexott

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs add explicit documentation about corner case
Projects
None yet
3 participants