-
Notifications
You must be signed in to change notification settings - Fork 398
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
Removed check for creation of Azure Key Vault-based databricks_secret_scope
using Service Principals
#1965
Removed check for creation of Azure Key Vault-based databricks_secret_scope
using Service Principals
#1965
Conversation
…n Databricks. It seems MSFT now fixed this issue. This commit removes the control that checks if the principal calling this is a Service Principal and throws an error.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #1965 +/- ##
=======================================
Coverage 90.29% 90.30%
=======================================
Files 146 146
Lines 11906 11895 -11
=======================================
- Hits 10751 10742 -9
+ Misses 746 745 -1
+ Partials 409 408 -1
|
databricks_secret_scope
using Service Principals
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.
we need to remove kvDiffFunc
completely
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.
lgtm. Integration tests are also passing
fyi @nfx
databricks_secret_scope
using Service Principalsdatabricks_secret_scope
using Service Principals
…t_scope` using Service Principals (databricks#1965) * With Service Principals was never possible to create a Secret Scope in Databricks. It seems MSFT now fixed this issue. This commit removes the control that checks if the principal calling this is a Service Principal and throws an error. * Removed unused function kvDiffFunc
This PR removes the check that was forbidding to call this from a Service Principal since it was not working. Now that MSFT fixed it we can remove the check and allow customers use it.