-
Notifications
You must be signed in to change notification settings - Fork 73
Description
Hi team,
I try to update new workflow in logic app using azapi_resource resource. I create 2 new API connection: one for office 365 connect and one for key vault connection.
For API key vault connection, I use client id and client secret. It will destroy and create again every time I trigger Terraform apply.
After I deploy, logic app can update, but I can not list the secrets in the key vault due to API connection for key vault is created before.
It only happen with v2.8.0. I downgrade and use v2.7.0, there is no issue.
I have add depends_on option to make sure API connection for key vault and office 365 are created before workflow is deployed
Here is the detail error:
module.logic_app_cs00178.azurerm_api_connection.keyvault["KeyVaultA"]: Destroying... [id
module.logic_app_cs00178.azurerm_api_connection.keyvault["KeyVaultA"]: Destruction complete after 1s
module.logic_app_cs00178.azurerm_api_connection.keyvault["KeyVaultB"]: Destroying...
module.logic_app_cs00178.azurerm_api_connection.keyvault["KeyVaultB"]: Destruction complete after 1s
module.logic_app_cs00178.azurerm_api_connection.keyvault["KeyVaultA"]: Creating...
module.logic_app_cs00178.azurerm_api_connection.keyvault["KeyVaultA"]: Creation complete after 1s
module.logic_app_cs00178.azurerm_api_connection.keyvault["KeyVaultB"]: Creating...
module.logic_app_cs00178.azurerm_api_connection.keyvault["KeyVaultB"]: Creation complete after 1s
module.logic_app_cs00178.azapi_resource.keyvault_expiration_check["kv_expiration_check_sandbox4sofa"]: Modifying...
│ Error: Missing Resource Identity After Update
│
│ with module.logic_app_cs00178.azapi_resource.keyvault_expiration_check["kv_expiration_check_sandbox4sofa"],
│ on ../../modules/generated/cs00178/logic_app/main.tf line 95, in resource "azapi_resource" "keyvault_expiration_check":
│ 95: resource "azapi_resource" "keyvault_expiration_check" {
│
│ The Terraform Provider unexpectedly returned no resource identity data
│ after having no errors in the resource update. This is always an issue in
│ the Terraform Provider and should be reported to the provider developers.