-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Error: "features": required field is not set #49458
Comments
In reading the terraform docs, include a features: {} in the provider: provider "azurerm" { |
Thanks for the feedback! We are currently investigating and will update you shortly. |
Hi, i'm getting the same error too at the same level. |
this issue seems to have been resolved in this link: hashicorp/terraform-provider-azurerm#5880 |
solution from terraform pages: https://www.terraform.io/docs/providers/azurerm/index.html configure the test.tf file to reflect the change below Configure the Azure Providerprovider "azurerm" { whilst the
|
Thanks for sharing the update. I have assigned the issue to the content author to investigate further and update the document as appropriate. @TomArcherMsft This information needs to be added to the documentation as it is causing the error. The details are provided here. |
@rudolfdobias Thanks for the feedback. We are updating all docs affected by the Terraform 2.0 release. |
Please update the DevOps documentation and Microsoft Learn links on automation too |
@rudolfdobias @robcamer This should be resolved. Please advise if not and will reopen. #please-close |
Following this tutorial results in this error on command terraform apply.
Additional info:
OS: Freshly installed Ubuntu 18.04 azure VM
Terraform:
v0.12.21
provider.azurerm v2.0.0
AZ:
{
"azure-cli": "2.1.0",
"azure-cli-command-modules-nspkg": "2.0.3",
"azure-cli-core": "2.1.0",
"azure-cli-nspkg": "3.0.4",
"azure-cli-telemetry": "1.0.4",
"extensions": {}
}
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: