delete veewee references. Veewee hasn't been updated for three years, and the veewee-to-packer library for even longer. This page gets almost no views.

website/content/guides/workflow-tips-and-tricks/veewee-to-packer.mdx

@@ -1,64 +0,0 @@
----
-page_title: Convert Veewee Definitions to Packer Templates - Guides
-description: |-
-  If you are or were a user of Veewee, then there is an official tool called
-  veewee-to-packer that will convert your Veewee definition into an equivalent
-  Packer template. Even if you're not a Veewee user, Veewee has a large library
-  of templates that can be readily used with Packer by simply converting them.
----
-
-# Veewee-to-Packer
-
-If you are or were a user of [Veewee](https://github.com/jedi4ever/veewee), then
-there is an official tool called
-[veewee-to-packer](https://github.com/mitchellh/veewee-to-packer) that will
-convert your Veewee definition into an equivalent Packer template. Even if
-you're not a Veewee user, Veewee has a [large
-library](https://github.com/jedi4ever/veewee/tree/master/templates) of templates
-that can be readily used with Packer by simply converting them.
-
-## Installation and Usage
-
-Since Veewee itself is a Ruby project, so too is the veewee-to-packer
-application so that it can read the Veewee configurations. Install it using
-RubyGems:
-
-```shell-session
-$ gem install veewee-to-packer
-# ...
-```
-
-Once installed, just point `veewee-to-packer` at the `definition.rb` file of any
-template. The converter will output any warnings or messages about the conversion.
-The example below converts a CentOS template:
-
-```shell-session
-$ veewee-to-packer templates/CentOS-6.4/definition.rb
-Success! Your Veewee definition was converted to a Packer
-template! The template can be found in the `template.json` file
-in the output directory: output
-
-Please be sure to run `packer validate` against the new template
-to verify settings are correct. Be sure to `cd` into the directory
-first, since the template has relative paths that expect you to
-use it from the same working directory.
-```
-
-**_Voila!_** By default, `veewee-to-packer` will output a template that contains
-a builder for both VirtualBox and VMware. You can use the `-only` flag on
-`packer build` to only build one of them. Otherwise you can use the `--builder`
-flag on `veewee-to-packer` to only output specific builder configurations.
-
-## Limitations
-
-None, really. The tool will tell you if it can't convert a part of a template,
-and whether that is a critical error or just a warning. Most of Veewee's
-functions translate perfectly over to Packer. There are still a couple missing
-features in Packer, but they're minimal.
-
-## Bugs
-
-If you find any bugs, please report them to the [veewee-to-packer issue
-tracker](https://github.com/mitchellh/veewee-to-packer). I haven't been able to
-exhaustively test every Veewee template, so there are certainly some edge cases
-out there.

website/data/guides-nav-data.json

@@ -56,10 +56,6 @@
         "title": "Isotime Template Function",
         "path": "workflow-tips-and-tricks/isotime-template-function"
       },
-      {
-        "title": "Veewee to Packer",
-        "path": "workflow-tips-and-tricks/veewee-to-packer"
-      },
       {
         "title": "Use jq to strip comments from a Packer template",
         "path": "workflow-tips-and-tricks/use-packer-with-comment"

website/redirects.next.js

@@ -24,11 +24,6 @@ module.exports = [
     destination: '/docs/builders/azure',
     permanent: true,
   },
-  {
-    source: '/docs/templates/veewee-to-packer',
-    destination: '/guides/veewee-to-packer',
-    permanent: true,
-  },
   {
     source: '/docs/extend/developing-plugins',
     destination: '/docs/plugins',