-
Notifications
You must be signed in to change notification settings - Fork 272
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
azuredevops_serviceendpoint_kubernetes plugin crashed #635
Comments
I got the I updated this using the AzureSubscription authorization type and it works without an crash: resource "azuredevops_serviceendpoint_kubernetes" "aks_endpoint" {
project_id = local.ado_project_id
service_endpoint_name = "mgmt-aks"
apiserver_url = format("https://%s:", azurerm_kubernetes_cluster.kubernetes.fqdn)
authorization_type = "AzureSubscription"
azure_subscription {
cluster_name = azurerm_kubernetes_cluster.kubernetes.name
subscription_id = data.azurerm_subscription.current.subscription_id
subscription_name = data.azurerm_subscription.current.display_name
tenant_id = data.azurerm_subscription.current.tenant_id
resourcegroup_id = azurerm_resource_group.resource_group.name
}
} Looks like the provider is handling the error response not well. |
I got the same error:
Downgrading the azure devops plugin to 0.2.1 helps, so I think this is a regression. When I use the same |
Community Note
Terraform (and Azure DevOps Provider) Version
Terraform v1.2.8
on linux_amd64
(run in tf cloud)
Affected Resource(s)
azuredevops_serviceendpoint_kubernetes
Terraform Configuration Files
Debug Output
https://gist.github.com/StefanSchoof/9d10a46d38a61a9df265e22635cc0fd3
Panic Output
Expected Behavior
no panic at apply (maybe error about credential)
Actual Behavior
plugin crash
Steps to Reproduce
terraform apply
Important Factoids
I have also a "state:Failed statusMessage:HandleAdalServiceExceptionFromRefreshTokenUse: Failed to obtain an access token of identity 533cf407-a69e-757e-8d23-d7d3ac3e1918 using cached refresh token. Sign-in required." in the log. Possible some credential problems are causing this crash. But even a wrong credential should not cause a crash.
References
The text was updated successfully, but these errors were encountered: