-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
New resource: azurerm_databricks_access_connector
#18709
New resource: azurerm_databricks_access_connector
#18709
Conversation
Thank you so much, @favoretti ! |
@tombuildsstuff One catch about this resource. Apparently SPN auth doesn't work with this API, only user-based auth. Wonder what to do about it.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this @favoretti! Since this is still in private preview I expected the tests to fail when trying to create the connector. Unfortunately it's created the connector in a failed state and currently can't be deleted. I'm going to mark this PR as blocked for the time being while we investigate this further.
Also just as an aside all resources within the provider will eventually need to be converted to typed resources for the gradual shift to using Pandora generated ones. Our contributor docs have a section on how to add new typed resources which will hopefully be helpful for future contributions 🙂.
internal/services/databricks/databricks_access_connector_resource.go
Outdated
Show resolved
Hide resolved
internal/services/databricks/databricks_access_connector_resource_test.go
Show resolved
Hide resolved
internal/services/databricks/validate/access_conector_name_test.go
Outdated
Show resolved
Hide resolved
internal/services/databricks/databricks_access_connector_resource.go
Outdated
Show resolved
Hide resolved
Thanks @stephybun. I completely blacked out on typed resources, I'll rewrite tomorrow, sorry about that. That failed connector will eventually be deletable. But the real reason it fails is that API doesn't work with SPN auth. I'm working with @nfx and team to see what the ETA is on supporting that. If persona authentication is used - resource works. |
@favoretti You say it's the same style of issue as creating the AKV scope for Databricks? 🫣 |
Also upgrade Databricks SDK to `2022-04-01-preview` I added acceptance tests, but feature is in private preview. Fixes hashicorp#18518
d393af9
to
d9963f1
Compare
@stephybun rewrote this, SPN thing is still under investigation, but can you please have another look code-wise? Thanks! |
@nfx Don't think so. AKV scope talks to Databricks DataPlane API, i.e. directly to the instance. This call is directed at management.azure.com, i.e. ARM API. Although you folks would know better, but I think this one should be easier to address. |
I hear SPN auth should be fixed. I'll retest today. |
Local acceptance tests pass, running TC now.
|
@stephybun should be good to go for another review and potential merge. Would you take a look? Thanks a lot! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor comments on the error messages, other this is good to go!
internal/services/databricks/databricks_access_connector_resource.go
Outdated
Show resolved
Hide resolved
internal/services/databricks/databricks_access_connector_resource.go
Outdated
Show resolved
Hide resolved
internal/services/databricks/databricks_access_connector_resource.go
Outdated
Show resolved
Hide resolved
internal/services/databricks/databricks_access_connector_resource.go
Outdated
Show resolved
Hide resolved
…rce.go Co-authored-by: stephybun <[email protected]>
…rce.go Co-authored-by: stephybun <[email protected]>
…rce.go Co-authored-by: stephybun <[email protected]>
…rce.go Co-authored-by: stephybun <[email protected]>
Thanks for the suggestions, @stephybun, committed, once unit tests complete, we should be gtg. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @favoretti LGTM 🧋
🥳 |
I am from Azure Databricks Product group and I see the conversation about creation failing with SPN and Private Preview of the resource. Let me clarify those two issues here.
We have received a customer escalation about the resource being documented as Private Preview. Can you help us understand the process to update this to Public Preview. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Also upgrade Databricks SDK to
2022-04-01-preview
Fixes #18518