Include link to Terraform repo in error messages about internal Terraform bugs

[gdavison]

Terraform Version

Terraform v1.13.3

Use Cases

When a Resource has no configuration error is returned by Terraform, the error message should point the user to the Terraform issue tracker

Attempted Solutions

N/A

Proposal

When a Resource has no configuration error is returned by Terraform, the error message includes This is a bug in Terraform; please report it!, the message should also include a link to the repo's issue tracker so that users will report the error to the correct project. They may instead open an issue in the provider issue tracker, e.g. hashicorp/terraform-provider-aws#44744

References

No response

[omarraf]

Hello! I've looked into this issue and would like to submit a PR to address it. I wanted to get some clarity before I start.

While investigating, I noticed there are many variations of the "This is a bug in Terraform" wording across the codebase. For example:

• "This is a bug in Terraform; please report it!"
• "This is a bug in Terraform and should be reported"
• "This is a bug in Terraform - please report it"

I had a few questions before proceeding:

1.) Should I focus only on the Resource has no configuration error as mentioned in this issue for now, or would you be open to a more comprehensive update that adds the issue-tracker link to all similar internal error messages?

2.) If doing a broader update is acceptable, should I also standardize the wording? For example using This is a bug in Terraform; please report it at https://github.com/hashicorp/terraform/issues

I’m happy to start with this specific error first and follow up with a separate PR or issue for broader message standardization if preferred. Thanks!