-
Notifications
You must be signed in to change notification settings - Fork 257
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
Provider Crash reading deleted Service Connection #918
Comments
Same issue with v.0.10.0
|
@FRUCHTiii This issue is bit tricky, normally if the service connection has been deleted service will return a result of http code 404. But in this scenario service returns the result with code 200 but response is |
@xuzhang3 Thanks for fixing this. Do you know when the next release will be that will include this fix? Also, is there a workaround for now? I've tried re-creating the service connection but the plugin is still crashing, unfortunately. Thanks! |
Actually, it looks like just removing the service connection from the state file does the trick. Looking forward to the next release, thanks! |
@AMoghrabi New version will be available in the early Dec |
We create service connections, elastic agent pools and needed queues via terraform.
The inital creation runs fine as expected. If I delete the agent pool manual afterwards and try to re-apply the terraform code to create the agent pools again the provider crashes and destroys the state.
It seems like the provider is crashing while reading the deleted service connection.
My expected behaviour where that the resources are created again.
I was able to reproduce this behaviour all the time. And I tested v0.9.1 and v0.10.0 of the terraform provider and run into the same issue.
I was not able to fix the terraform state afterwards. So I had to restore an old state file.
Community Note
Terraform (and Azure DevOps Provider) Version
microsoft/azuredevops v0.9.1
microsoft/azuredevops v0.10.0
terraform v1.5.7
Affected Resource(s)
azuredevops_serviceendpoint_azurerm
Terraform Configuration Files
Debug Output
Expected Behavior
Recreate the deleted resources
Actual Behavior
Crash of the provider
Steps to Reproduce
References
crash.log
The text was updated successfully, but these errors were encountered: