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

Removed check for creation of Azure Key Vault-based databricks_secret_scope using Service Principals #1965

Merged
merged 3 commits into from
Jan 30, 2023

Conversation

mattiazenidb
Copy link
Contributor

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.

mattiazenidb and others added 2 commits January 27, 2023 20:56
…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-commenter
Copy link

codecov-commenter commented Jan 27, 2023

Codecov Report

Merging #1965 (9c77674) into master (8660c0f) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@           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     
Impacted Files Coverage Δ
secrets/resource_secret_scope.go 92.30% <ø> (+1.83%) ⬆️

@mattiazenidb mattiazenidb changed the title Allow creation on Secret Scope using a Service Principal Allow creation of Secret Scope using a Service Principal Jan 27, 2023
@mattiazenidb mattiazenidb changed the title Allow creation of Secret Scope using a Service Principal Allow creation of Secret Scopes using Service Principals Jan 27, 2023
@alexott alexott changed the title Allow creation of Secret Scopes using Service Principals Remove check for creation of Azure Key Vault-based databricks_secret_scope using Service Principals Jan 30, 2023
Copy link
Contributor

@alexott alexott left a 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

secrets/resource_secret_scope.go Show resolved Hide resolved
Copy link
Contributor

@alexott alexott left a 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

@nfx nfx changed the title Remove check for creation of Azure Key Vault-based databricks_secret_scope using Service Principals Removed check for creation of Azure Key Vault-based databricks_secret_scope using Service Principals Jan 30, 2023
@nfx nfx merged commit e6546fc into databricks:master Jan 30, 2023
@nfx nfx mentioned this pull request Feb 3, 2023
michael-berk pushed a commit to michael-berk/terraform-provider-databricks that referenced this pull request Feb 15, 2023
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants