Create bug_report.yml

Author: jacobbednarz

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,118 @@
+name: "\U0001F41B Bug report"
+description: "When something isn't working as expected or documented"
+labels: ["kind/bug", "needs-triage"]
+body:
+- type: markdown
+  attributes:
+    value: |
+      Thank you for opening an issue. Please note that we try to keep the 
+      Terraform issue tracker reserved for bug reports and feature requests. 
+      For general usage questions, please see: https://www.terraform.io/community.html.
+- type: checkboxes
+  attributes:
+    label: Confirmation
+    description: Please make sure to have followed the following checks.
+    options:
+      - label: This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team. 
+        required: true
+      - label: I have searched the issue tracker and my issue isn't already found.
+        required: true
+      - label: I have replicated my issue using the latest version of the provider and it is still present.
+        required: true
+- type: textarea
+  attributes:
+    label: Terraform and Cloudflare provider version
+    description: |
+      Run `terraform -v` to show the version of Terraform and providers you are 
+      using. If you are not running the latest version of Terraform or the 
+      providers, please upgrade because your issue may have already been fixed.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Affected resource(s)
+    description: |
+      Please list the resources as a list, for example:
+      - opc_instance
+      - opc_storage_volume
+
+      If this issue appears to affect multiple resources, it may be an issue with
+      Terraform's core, so please mention this.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Terraform configuration files
+    description: |
+      No need for code block backticks, this will be rendered as HCL automatically. 
+      
+      Avoid using `for` loops, dynamics or data sources in your examples as they 
+      do not make for a good reproduction test case and may contain bugs in the 
+      expressions used.
+      
+      If you cannot provide your exact configuration due to sensitivity, please
+      provide a minimal reproduction case that demonstrates your issue with the setup
+      you are using.
+    placeholder: |
+      resource "example_resource" "my_resource" {
+        # ..
+      }
+    render: hcl
+  validations:
+    required: true
+- type: input
+  attributes:
+    label: Link to debug output
+    description: |
+      A link to the output (https://gist.github.com) provided from prepending `TF_LOG=DEBUG` to your 
+      Terraform apply or plan.  **Do not truncate or trim the output as the surrounding context 
+      is useful for debugging and without it, maintainers are restricted in what assistance and 
+      diagnosis they can provide**. 
+      
+      Be sure to redact or sanitise any sensitive information (such as API keys or tokens) in 
+      your logs. https://jacobbednarz.com/tf-log-redactor/ is an online tool that will handle
+      redacting the sensitive Cloudflare details from your log output for you if you don't want
+      to manually do it. Provider versions newer than v3.32.0 automatically redacts all Cloudflare
+      credentials.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Panic output
+    description: Output from a crash or Go panic.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Expected output
+    description: What did you expect to happen?
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Actual output
+    description: What actually happened?
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Steps to reproduce
+    description: How can your issue be replicated?
+    placeholder: |
+      1. ...
+      2. ...
+      3. ...
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Additional factoids
+    description: Is there any other important information you'd like to share?
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: References
+    description: Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? 
+  validations:
+    required: false