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

[FEATURE] databricks_connection without including credentials in the Terraform setup #4327

Open
sduveen-pivot opened this issue Dec 16, 2024 · 2 comments
Labels
feature New feature or request public api affects terraform provider schema or behaviour

Comments

@sduveen-pivot
Copy link

Use-cases

We enjoy for all other objects we maintain in our Terraform setup for databricks not having any credentials/passwords maintained within it. E.g. We creeate secret scopes w/permissions, but not the secrets themselves.
Unfortunately, for the connections it requires the credentials while creating the resource.
It would be wonderful if we could e.g. reference a databricks secret for the connection options OR leave it unset and then if we modify it in the console, not for those additional options to be removed (I'd prefer the former secrets link)

Attempted Solutions

Proposal

References

https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/connection

@sduveen-pivot sduveen-pivot added the feature New feature or request label Dec 16, 2024
@alexott alexott added the public api affects terraform provider schema or behaviour label Jan 2, 2025
@alexott
Copy link
Contributor

alexott commented Jan 2, 2025

It's really a limitation of the APIs - the actual payload expected by API is just a map that terraform needs to send. If some parameters aren't provided then API rejects it...

@sduveen-pivot
Copy link
Author

I understand the API-limiting aspect. I'm hoping you have some access to the API team, for instance ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request public api affects terraform provider schema or behaviour
Projects
None yet
Development

No branches or pull requests

2 participants