Add hashibot configuration for transferring issues

The added configuration will allow us to transfer open remote-plugin/* issues from hashicorp/packer to their new respective repos. HashiBot issue transfer only works with orgs it has write access to. Which is similar to how GitHub's issue transfer feature works.
fix error messaging in wrappedmain. Stderr gets eaten by panicwrap, so we need to write to stdout, which then gets unpacked into error and output messages using the ErrorPrefix and OutputPrefix (#10766 )
2021-03-18 17:14:13 -04:00 · 2021-03-16 11:21:00 +01:00
2 changed files with 19 additions and 13 deletions
@@ -22,3 +22,21 @@ poll "closed_issue_locker" "locker" {
    If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
  EOF
 }
+
+poll "label_issue_migrater" "remote_plugin_migrater" {
+  schedule                = "0 20 * * * *"
+  new_owner               = "hashicorp"
+  repo_prefix             = "packer-plugin-"
+  label_prefix            = "remote-plugin/"
+  excluded_label_prefixes  = ["communicator/"]
+  excluded_labels         = ["build", "core", "new-plugin-contribution", "website"]
+
+  issue_header     = <<-EOF
+    _This issue was originally opened by @${var.user} as ${var.repository}#${var.issue_number}. It was migrated here as a result of the [Packer plugin split](###blog-post-url###). The original body of the issue is below._
+
+    <hr>
+
+    EOF
+  migrated_comment = "This issue has been automatically migrated to ${var.repository}#${var.issue_number} because it looks like an issue with that plugin. If you believe this is _not_ an issue with the plugin, please reply to ${var.repository}#${var.issue_number}."
+}
+
@@ -51,7 +51,7 @@ Packer files. The config dir of packer will be looked up on the following paths:
 |-----------------------------|-----------------------------|
 | `PACKER_HOME_DIR/.packer.d` | `PACKER_HOME_DIR/packer.d/` |

-Examples:
+Examples: 
 * On a 'unix' system, if the `$PACKER_CONFIG_DIR` env var is set to
 `/home/packer`, the config directory will be: `/home/packer/.packer.d/` and
 other values will not be checked.
@@ -94,18 +94,6 @@ configuration file. None of these are required, since all have defaults.
  and the [`packer init`](/docs/commands/init) command to install plugins; if
  you are using both, the `required_plugin` config will take precedence.

-Example Packer config:
-
-```
-{
-  "plugin_min_port": 11000,
-  "plugin_max_port": 25000,
-  "provisioners": {
-    "foo": "/Users/example/packer-provisioner-foo"
-  }
-}
-```
-
 ## Full list of Environment Variables usable for Packer

 Packer uses a variety of environmental variables. A listing and description of
Author	SHA1	Message	Date
Wilken Rivera	1347a122cf	Add hashibot configuration for transferring issues The added configuration will allow us to transfer open remote-plugin/* issues from hashicorp/packer to their new respective repos. HashiBot issue transfer only works with orgs it has write access to. Which is similar to how GitHub's issue transfer feature works.	2021-03-18 17:14:13 -04:00
Megan Marsh	64a3219f69	fix error messaging in wrappedmain. Stderr gets eaten by panicwrap, so we need to write to stdout, which then gets unpacked into error and output messages using the ErrorPrefix and OutputPrefix (#10766 )	2021-03-16 11:21:00 +01:00