bug_report.yml
bug_report.yml
Name | About | Labels | Assignees |
---|---|---|---|
Bug Report | Let us know about an unexpected error, a crash, or an incorrect behavior. | bug,new |
Thank you for opening an issue.
The hashicorp/terraform issue tracker is reserved for bug reports relating to the core Terraform CLI application and configuration language.
For general usage questions, please see: https://www.terraform.io/community.html.
If your issue relates to:
- Terraform Cloud/Enterprise: please email tf-cloud@hashicorp.support or open a new request.
- AWS Terraform Provider: Open an issue at hashicorp/terraform-provider-aws.
- Azure Terraform Provider: Open an issue at hashicorp/terraform-provider-azurerm.
- Other Terraform Providers: Please open an issue in the provider's own repository, which can be found by searching the Terraform Registry.
Filing a bug report
To fix problems, we need clear reproduction cases - we need to be able to see it happen locally. A reproduction case is ideally something a Terraform Core engineer can git-clone or copy-paste and run immediately, without inventing any details or context.
- A short example can be directly copy-pasteable; longer examples should be in separate git repositories, especially if multiple files are needed
- Please include all needed context. For example, if you figured out that an expression can cause a crash, put the expression in a variable definition or a resource
- Set defaults on (or omit) any variables. The person reproducing it should not need to invent variable settings
- If multiple steps are required, such as running terraform twice, consider scripting it in a simple shell script. Providing a script can be easier than explaining what changes to make to the config between runs.
- Omit any unneeded complexity: remove variables, conditional statements, functions, modules, providers, and resources that are not needed to trigger the bug
- When possible, use the null resource provider rather than a real provider in order to minimize external dependencies. We know this isn't always feasible. The Terraform Core team doesn't have deep domain knowledge in every provider, or access to every cloud platform for reproduction cases.
Note: If the submit button is disabled and you have filled out all required fields, please check that you did not forget a Title for the issue.