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

[ISSUE] service_principal resource errors out after 0.5.3 upgrade #1193

Closed
vadivelselvaraj opened this issue Mar 15, 2022 · 3 comments · Fixed by #1194
Closed

[ISSUE] service_principal resource errors out after 0.5.3 upgrade #1193

vadivelselvaraj opened this issue Mar 15, 2022 · 3 comments · Fixed by #1194

Comments

@vadivelselvaraj
Copy link

vadivelselvaraj commented Mar 15, 2022

After upgrading from databricks provider from 0.4.9 to 0.5.3, I see the below error during the planning phase.

Error: application_id is not allowed for service principals in Databricks on AWS
with databricks_service_principal.deployment_user
on service_principals.tf line 1, in resource "databricks_service_principal" "deployment_user":
resource "databricks_service_principal" "deployment_user" {

Below is my config. And this doesn't include application_id as the error states.

resource "databricks_service_principal" "deployment_user" {
  display_name         = "deployment-user"
  allow_cluster_create = true
}

This is an AWS Databricks deployment btw.

Any suggestion on how to fix this?

@vadivelselvaraj
Copy link
Author

@nfx Likely linked to your changes in #1165

@nfx
Copy link
Contributor

nfx commented Mar 15, 2022

@vadivelselvaraj More like because of this 8c0a19e

Need to remove validation completely and defer it to API. Update to 0.5.2

Can you build provider locally?

nfx added a commit that referenced this issue Mar 15, 2022
Users will receive a bit more crypting message, but things will work in a more predictable way.

Fix #1193
@nfx nfx closed this as completed in #1194 Mar 15, 2022
nfx added a commit that referenced this issue Mar 15, 2022
…l` (#1194)

Users will receive a bit more crypting message, but things will work in a more predictable way.

Fix #1193
@nfx
Copy link
Contributor

nfx commented Mar 15, 2022

@vadivelselvaraj please build from master to get a fix before next release.

@databricks databricks locked and limited conversation to collaborators Mar 15, 2022
michael-berk pushed a commit to michael-berk/terraform-provider-databricks that referenced this issue Feb 15, 2023
…l` (databricks#1194)

Users will receive a bit more crypting message, but things will work in a more predictable way.

Fix databricks#1193
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants