Closed chopeen closed 1 week ago
Hi @chopeen. Azure Verified Modules do not explicitly support OpenTofu and we don't test with OpenTofu. This is the first issue I have seen where there is a difference between the OpenTofu and Terraform CLI implementations that is surfacing as an issue. This is very interesting to see and I will raise with the other AVM leads to get their thoughts. Unfortunately, there is nothing we can do to resolve this in the short term.
CC @matt-FFFFFF @jtracey93
I was going to post exactly what @jaredfholgate did!
I suggest opening an issue on the opentofu repo to support this.
At the moment we are reliant on opentofu's compatibility promises. We will consider as a team if we need to change our position
If we choose to support both then it's a race to the bottom in terms of the features we can use.
I think you're both right - OpenTofu does support the removed
block, but not the lifecycle
meta-argument in modules - there is an open feature request https://github.com/opentofu/opentofu/issues/304 for such enhancement.
GitLab has deprecated support for the Terraform templates (see deprecate-terraform-cicd-templates) and stopped updating terraform
binaries licensed under BSL; Terraform CI/CD templates will be removed completely in May 2025.
Can you please discuss the possibility of adding support for OpenTofu?
Is there an existing issue for this?
Greenfield/Brownfield provisioning
brownfield
Terraform Version
OpenTofu v1.8.1
Module Version
0.2.5
AzureRM Provider Version
v3.116.0
Affected Resource(s)/Data Source(s)
?
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
No response
Actual Behaviour
After upgrading from
0.2.4
->0.2.5
, bothtofu init
andtofu validate
are failing with error Blocks of type "lifecycle" are not expected here.Steps to Reproduce
No response
Important Factoids
No response
References
No response