Maciek

Results 9 comments of Maciek

`virtual_network_subnet_id` is always reset when connecting to virtual network using `azurerm_app_service_virtual_network_swift_connection`

Looks like https://github.com/hashicorp/terraform-provider-azurerm/issues/17930#issuecomment-1216719591 is the "solution" :/

retention_in_days setting falsely removed on any other change in linux_web_app

any progress on this?

`virtual_network_subnet_id` is always reset when connecting to virtual network using `azurerm_app_service_virtual_network_swift_connection`

in v3.74.0. still there

`virtual_network_subnet_id` is always reset when connecting to virtual network using `azurerm_app_service_virtual_network_swift_connection`

The [documentation](https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle) says > In some rare cases, settings of a remote object are modified by processes outside of Terraform, which Terraform would then attempt to "fix" on the next...

v1.8 says Backend configuration block has changed when it hasn't

The same error is shown for Azure storage account backend with terraform 1.8.5 Any hints or fix @apparentlymart ?

v1.8 says Backend configuration block has changed when it hasn't

Adding the parameter below seemed to solved the problem for me `backendAzureRmUseEnvironmentVariablesForAuthentication: true` ``` - task: TerraformTaskV4@4 displayName: 'init' inputs: provider: 'azurerm' command: 'init' workingDirectory: '$(System.DefaultWorkingDirectory)/terraform/' backendAzureRmUseEnvironmentVariablesForAuthentication: true backendServiceArm: '$(servicePrincipal)'...

HTTP response was nil; connection may have been reset

the same for terraform creating 4 resources ``` Terraform v1.9.7 on darwin_arm64 + provider registry.terraform.io/hashicorp/azurerm v4.5.0 ```

change noise with cross_origin_auth

Hey, we have the same issue. Why `terraform apply` does not remove `cross_origin_auth` from the state?

change noise with cross_origin_auth

You might be right with the schema. However updating all the code with optional optional field with the default value just to _satisfy_ the provider does not bring much value....