remove layout frontmatter prop
This commit is contained in:
Jeff Escalante
parent
2de270341c
commit
25380116f2
|
|
@ -1,13 +0,0 @@
|
|||
// This script removes the "sidebar_current" key from frontmatter, as it is
|
||||
// no longer needed.
|
||||
|
||||
const glob = require('glob')
|
||||
const path = require('path')
|
||||
const fs = require('fs')
|
||||
const matter = require('gray-matter')
|
||||
|
||||
glob.sync(path.join(__dirname, './content/**/*.mdx')).map((fullPath) => {
|
||||
let { content, data } = matter.read(fullPath)
|
||||
delete data.layout
|
||||
fs.writeFileSync(fullPath, matter.stringify(content, data))
|
||||
})
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
page_title: Download Packer Community Projects
|
||||
description:
|
||||
description: >-
|
||||
Packer has a vibrant community of contributors who have built a number of
|
||||
great tools on top of Packer. There are also quite a few projects
|
||||
demonstrating the power of Packer templates.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The `alicloud-ecs` Packer builder plugin provide the capability to build
|
||||
customized images based on an existing base images.
|
||||
layout: docs
|
||||
page_title: Alicloud Image Builder
|
||||
sidebar_title: Alicloud ECS
|
||||
---
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ description: >
|
|||
instance storage and EBS-backed instances, storage for the root device section
|
||||
|
||||
in the EC2 documentation.
|
||||
layout: docs
|
||||
page_title: Amazon chroot - Builders
|
||||
sidebar_title: chroot
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: |
|
|||
volumes for use in EC2. For more information on the difference between
|
||||
EBS-backed instances and instance-store backed instances, see the storage for
|
||||
the root device section in the EC2 documentation.
|
||||
layout: docs
|
||||
page_title: Amazon EBS - Builders
|
||||
sidebar_title: EBS
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: >
|
|||
not
|
||||
|
||||
require running inside an EC2 instance.
|
||||
layout: docs
|
||||
page_title: Amazon EBS Surrogate - Builders
|
||||
sidebar_title: EBS Surrogate
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The amazon-ebsvolume Packer builder is like the EBS builder, but is
|
||||
intended to create EBS volumes rather than a machine image.
|
||||
layout: docs
|
||||
page_title: Amazon EBS Volume - Builders
|
||||
sidebar_title: EBS Volume
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
Packer is able to create Amazon AMIs. To achieve this, Packer comes with
|
||||
multiple builders depending on the strategy you want to use to build the AMI.
|
||||
layout: docs
|
||||
page_title: Amazon AMI - Builders
|
||||
sidebar_title: Amazon EC2
|
||||
---
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ description: >
|
|||
root
|
||||
|
||||
device section in the EC2 documentation.
|
||||
layout: docs
|
||||
page_title: Amazon instance-store - Builders
|
||||
sidebar_title: Instance
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,6 +1,5 @@
|
|||
---
|
||||
description: Packer supports building VHDs in Azure Resource manager.
|
||||
layout: docs
|
||||
page_title: Azure arm - Builders
|
||||
sidebar_title: ARM
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: >
|
|||
leveraging
|
||||
|
||||
a VM in Azure.
|
||||
layout: docs
|
||||
page_title: Azure chroot - Builders
|
||||
sidebar_title: chroot
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: >
|
|||
|
||||
multiple builders depending on the strategy you want to use to build the
|
||||
images.
|
||||
layout: docs
|
||||
page_title: Azure images - Builders
|
||||
sidebar_title: Azure
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: |
|
|||
CloudStack. The builder takes either an ISO or an existing template as it's
|
||||
source, runs any provisioning necessary on the instance after launching it and
|
||||
then creates a new template from that instance.
|
||||
layout: docs
|
||||
page_title: CloudStack - Builders
|
||||
sidebar_title: CloudStack
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
Community-maintained builders are not part of the core Packer binary, but
|
||||
can run alongside Packer with minimal extra effort.
|
||||
layout: docs
|
||||
page_title: Community - Builders
|
||||
sidebar_title: Community-Supported
|
||||
---
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ description: |
|
|||
Packer is extensible, allowing you to write new builders without having to
|
||||
modify the core source code of Packer itself. Documentation for creating new
|
||||
builders is covered in the custom builders page of the Packer plugin section.
|
||||
layout: docs
|
||||
page_title: Custom - Builders
|
||||
sidebar_title: Custom
|
||||
---
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ description: >
|
|||
reusable image can then be used as the foundation of new servers that are
|
||||
|
||||
launched within DigitalOcean.
|
||||
layout: docs
|
||||
page_title: DigitalOcean - Builders
|
||||
sidebar_title: DigitalOcean
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ description: >
|
|||
a Docker container, runs provisioners within this container, then exports the
|
||||
|
||||
container for reuse or commits the image.
|
||||
layout: docs
|
||||
page_title: Docker - Builders
|
||||
sidebar_title: Docker
|
||||
---
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ description: |
|
|||
The file Packer builder is not really a builder, it just creates an artifact
|
||||
from a file. It can be used to debug post-processors without incurring high
|
||||
wait times.
|
||||
layout: docs
|
||||
page_title: File - Builders
|
||||
sidebar_title: File
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The googlecompute Packer builder is able to create images for use with Google
|
||||
Cloud Compute Engine (GCE) based on existing images.
|
||||
layout: docs
|
||||
page_title: Google Compute - Builders
|
||||
sidebar_title: Google Cloud
|
||||
---
|
||||
|
|
|
|||
|
|
@ -5,7 +5,6 @@ description: |
|
|||
necessary on the image after launching it, then snapshots it into a reusable
|
||||
image. This reusable image can then be used as the foundation of new servers
|
||||
that are launched within the Hetzner Cloud.
|
||||
layout: docs
|
||||
page_title: Hetzner Cloud - Builders
|
||||
sidebar_title: Hetzner Cloud
|
||||
---
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ description: |
|
|||
HyperOne Packer builder creates new images on the HyperOne platform.
|
||||
The builder takes a source image, runs any provisioning necessary on
|
||||
the image after launching it, then creates a reusable image.
|
||||
layout: docs
|
||||
page_title: HyperOne - Builders
|
||||
sidebar_title: HyperOne
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The Hyper-V Packer builder is able to create Hyper-V virtual machines and
|
||||
export them.
|
||||
layout: docs
|
||||
page_title: Hyper-V - Builders
|
||||
sidebar_title: Hyper-V
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ modeline: |
|
|||
description: |
|
||||
The Hyper-V Packer builder is able to create Hyper-V virtual machines and
|
||||
export them.
|
||||
layout: docs
|
||||
page_title: Hyper-V ISO - Builders
|
||||
sidebar_title: ISO
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ modeline: |
|
|||
description: >-
|
||||
The Hyper-V Packer builder is able to clone an existing Hyper-V virtual
|
||||
machine and export them.
|
||||
layout: docs
|
||||
page_title: Hyper-V Builder (from a vmcx)
|
||||
sidebar_title: VMCX
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
Builders are responsible for creating machines and generating images from them
|
||||
for various platforms.
|
||||
layout: docs
|
||||
page_title: Builders
|
||||
sidebar_title: Builders
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The `jdcloud` Packer builder helps you to build instance images
|
||||
based on an existing image
|
||||
layout: docs
|
||||
page_title: JDCloud Image Builder
|
||||
sidebar_title: JDCloud
|
||||
---
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ description: >
|
|||
image can then be used as the foundation of new servers that are launched
|
||||
|
||||
within all Linode regions.
|
||||
layout: docs
|
||||
page_title: Linode - Builders
|
||||
sidebar_title: Linode
|
||||
---
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ description: |
|
|||
The `lxc` Packer builder builds containers for lxc1. The builder starts an LXC
|
||||
container, runs provisioners within this container, then exports the container
|
||||
as a tar.gz of the root file system.
|
||||
layout: docs
|
||||
page_title: LXC - Builders
|
||||
sidebar_title: LXC
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ description: >
|
|||
as
|
||||
|
||||
an LXD image.
|
||||
layout: docs
|
||||
page_title: LXD - Builders
|
||||
sidebar_title: LXD
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The ncloud builder allows you to create server images using the NAVER Cloud
|
||||
Platform.
|
||||
layout: docs
|
||||
page_title: Naver Cloud Platform - Builders
|
||||
sidebar_title: NAVER Cloud
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: |
|
|||
connection and runs the provisioners. It can be used to debug provisioners
|
||||
without incurring high wait times. It does not create any kind of image or
|
||||
artifact.
|
||||
layout: docs
|
||||
page_title: Null - Builders
|
||||
sidebar_title: 'Null'
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,6 +1,5 @@
|
|||
---
|
||||
description: The 1&1 builder is able to create images for 1&1 cloud.
|
||||
layout: docs
|
||||
page_title: 1&1 - Builders
|
||||
sidebar_title: 1&1
|
||||
---
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ description: >
|
|||
image can then be used as the foundation of new servers that are launched
|
||||
|
||||
within OpenStack.
|
||||
layout: docs
|
||||
page_title: OpenStack - Builders
|
||||
sidebar_title: OpenStack
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The oracle-classic builder is able to create new custom images for use with
|
||||
Oracle Cloud Infrastructure Classic Compute.
|
||||
layout: docs
|
||||
page_title: Oracle Cloud Infrastructure Classic - Builders
|
||||
sidebar_title: Oracle Classic
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,6 +1,5 @@
|
|||
---
|
||||
description: Packer is able to create custom images using Oracle Cloud Infrastructure.
|
||||
layout: docs
|
||||
page_title: Oracle - Builders
|
||||
sidebar_title: Oracle
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The oracle-oci builder is able to create new custom images for use with Oracle
|
||||
Cloud Infrastructure (OCI).
|
||||
layout: docs
|
||||
page_title: Oracle OCI - Builders
|
||||
sidebar_title: Oracle OCI
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ description: >
|
|||
BSU-backed VMs and VM-store backed VMs, see the storage for
|
||||
|
||||
the root device section in the Outscale documentation.
|
||||
layout: docs
|
||||
page_title: Outscale BSU - Builders
|
||||
sidebar_title: BSU
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The osc-bsusurrogate Packer builder is like the chroot builder, but does not
|
||||
require running inside an Outscale virtual machine.
|
||||
layout: docs
|
||||
page_title: Outscale BSU Surrogate - Builders
|
||||
sidebar_title: BSU Surrogate
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The osc-bsuvolume Packer builder is like the BSU builder, but is intended to
|
||||
create BSU volumes rather than a machine image.
|
||||
layout: docs
|
||||
page_title: Outscale BSU Volume - Builders
|
||||
sidebar_title: BSU Volume
|
||||
---
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ description: >
|
|||
instance storage and BSU-backed instances, storage for the root device section
|
||||
|
||||
in the Outscale documentation.
|
||||
layout: docs
|
||||
page_title: Outscale chroot - Builders
|
||||
sidebar_title: chroot
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: >
|
|||
Packer comes with
|
||||
|
||||
multiple builders depending on the strategy you want to use to build the OMI.
|
||||
layout: docs
|
||||
page_title: Outscale OMI - Builders
|
||||
sidebar_title: Outscale
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The Parallels Packer builder is able to create Parallels Desktop for Mac
|
||||
virtual machines and export them in the PVM format.
|
||||
layout: docs
|
||||
page_title: Parallels - Builders
|
||||
sidebar_title: Parallels
|
||||
---
|
||||
|
|
|
|||
|
|
@ -5,7 +5,6 @@ description: |
|
|||
The Parallels Packer builder is able to create Parallels Desktop for Mac
|
||||
virtual machines and export them in the PVM format, starting from an ISO
|
||||
image.
|
||||
layout: docs
|
||||
page_title: Parallels ISO - Builders
|
||||
sidebar_title: ISO
|
||||
---
|
||||
|
|
|
|||
|
|
@ -5,7 +5,6 @@ description: |
|
|||
This Parallels builder is able to create Parallels Desktop for Mac virtual
|
||||
machines and export them in the PVM format, starting from an existing PVM
|
||||
(exported virtual machine image).
|
||||
layout: docs
|
||||
page_title: Parallels PVM - Builders
|
||||
sidebar_title: PVM
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,6 +1,5 @@
|
|||
---
|
||||
description: The ProfitBricks builder is able to create images for ProfitBricks cloud.
|
||||
layout: docs
|
||||
page_title: ProfitBricks - Builders
|
||||
sidebar_title: ProfitBricks
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: |
|
|||
Proxmox VE. The builder takes a cloud-init enabled virtual machine
|
||||
template name, runs any provisioning necessary on the image after
|
||||
launching it, then creates a virtual machine template.
|
||||
layout: docs
|
||||
page_title: Proxmox Clone - Builders
|
||||
sidebar_title: Clone
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,9 +1,7 @@
|
|||
---
|
||||
description: >
|
||||
The Proxmox Packer builder is able to create Cloud-Init
|
||||
virtual machine images on a Proxmox server.
|
||||
|
||||
layout: docs
|
||||
The Proxmox Packer builder is able to create Cloud-Init virtual machine images
|
||||
on a Proxmox server.
|
||||
page_title: Proxmox - Builders
|
||||
sidebar_title: Proxmox
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: |
|
|||
Proxmox VE. The builder takes an ISO source, runs any provisioning
|
||||
necessary on the image after launching it, then creates a virtual machine
|
||||
template.
|
||||
layout: docs
|
||||
page_title: Proxmox ISO - Builders
|
||||
sidebar_title: ISO
|
||||
---
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ modeline: |
|
|||
vim: set ft=pandoc:
|
||||
description: |
|
||||
The Qemu Packer builder is able to create KVM virtual machine images.
|
||||
layout: docs
|
||||
page_title: QEMU - Builders
|
||||
sidebar_title: QEMU
|
||||
---
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ description: >
|
|||
new
|
||||
|
||||
servers that are launched within Scaleway.
|
||||
layout: docs
|
||||
page_title: Scaleway - Builders
|
||||
sidebar_title: Scaleway
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The `tencentcloud-cvm` Packer builder plugin provide the capability to build
|
||||
customized images based on an existing base images.
|
||||
layout: docs
|
||||
page_title: Tencentcloud Image Builder
|
||||
sidebar_title: Tencent Cloud
|
||||
---
|
||||
|
|
|
|||
|
|
@ -9,7 +9,6 @@ description: >
|
|||
Triton
|
||||
|
||||
Cloud API to create images.
|
||||
layout: docs
|
||||
page_title: Triton - Builders
|
||||
sidebar_title: Triton
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The `ucloud-uhost` Packer builder plugin provides the capability to build
|
||||
customized images based on an existing base image for use in UHost Instance.
|
||||
layout: docs
|
||||
page_title: UCloud Image Builder
|
||||
sidebar_title: UCloud
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The Vagrant Packer builder is able to launch Vagrant boxes and
|
||||
re-package them into .box files
|
||||
layout: docs
|
||||
page_title: Vagrant - Builders
|
||||
sidebar_title: Vagrant
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: >
|
|||
and
|
||||
|
||||
export them in the OVA or OVF format.
|
||||
layout: docs
|
||||
page_title: VirtualBox - Builders
|
||||
sidebar_title: VirtualBox
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ modeline: |
|
|||
description: |
|
||||
The VirtualBox Packer builder is able to create VirtualBox virtual machines
|
||||
and export them in the OVF format, starting from an ISO image.
|
||||
layout: docs
|
||||
page_title: VirtualBox ISO - Builders
|
||||
sidebar_title: ISO
|
||||
---
|
||||
|
|
|
|||
|
|
@ -5,7 +5,6 @@ description: |
|
|||
This VirtualBox Packer builder is able to create VirtualBox virtual machines
|
||||
and export them in the OVF format, starting from an existing OVF/OVA (exported
|
||||
virtual machine image).
|
||||
layout: docs
|
||||
page_title: VirtualBox OVF/OVA - Builders
|
||||
sidebar_title: OVF
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ description: >
|
|||
snapshots
|
||||
|
||||
and export them in the OVF format, starting from an ISO image.
|
||||
layout: docs
|
||||
page_title: VirtualBox Snapshot - Builders
|
||||
sidebar_title: VM
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The VMware Packer builder is able to create VMware virtual machines for use
|
||||
with any VMware product.
|
||||
layout: docs
|
||||
page_title: VMware - Builders
|
||||
sidebar_title: VMware
|
||||
---
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ description: |
|
|||
running VMware Fusion for OS X, VMware Workstation for Linux and Windows, and
|
||||
VMware Player on Linux. It can also build machines directly on VMware vSphere
|
||||
Hypervisor using SSH as opposed to the vSphere API.
|
||||
layout: docs
|
||||
page_title: VMware ISO - Builders
|
||||
sidebar_title: VMWare ISO
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,6 @@ description: |
|
|||
existing VMware virtual machine (a VMX file). It currently supports building
|
||||
virtual machines on hosts running VMware Fusion Professional for OS X, VMware
|
||||
Workstation for Linux and Windows, and VMware Player on Linux.
|
||||
layout: docs
|
||||
page_title: VMware VMX - Builders
|
||||
sidebar_title: VMWare VMX
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ modeline: |
|
|||
description: >
|
||||
This VMware Packer builder uses the vSphere API to clone an existing vSphere
|
||||
template and create a new virtual machine remotely.
|
||||
layout: docs
|
||||
page_title: VSphere Clone - Builders
|
||||
sidebar_title: VSphere Clone
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ modeline: |
|
|||
description: |
|
||||
This VMware Packer builder starts from an ISO and creates a vm using the
|
||||
vSphere API to build on a remote VMWare machine.
|
||||
layout: docs
|
||||
page_title: VSphere ISO - Builders
|
||||
sidebar_title: VSphere ISO
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The yandex Packer builder is able to create images for use with
|
||||
Yandex.Cloud based on existing images.
|
||||
layout: docs
|
||||
page_title: Yandex Compute - Builders
|
||||
sidebar_title: Yandex.Cloud
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: |
|
|||
in order to generate a set of artifacts. The various builds specified within a
|
||||
template are executed in parallel, unless otherwise specified. And the
|
||||
artifacts that are created will be outputted at the end of the build.
|
||||
layout: docs
|
||||
page_title: packer build - Commands
|
||||
sidebar_title: <tt>build</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The `packer console` command allows you to experiment with Packer variable
|
||||
interpolations.
|
||||
layout: docs
|
||||
page_title: packer console - Commands
|
||||
sidebar_title: <tt>console</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: |
|
|||
parts of it and brings it up to date so it can be used with the latest version
|
||||
of Packer. After you update to a new Packer release, you should run the fix
|
||||
command to make sure your templates work with the new release.
|
||||
layout: docs
|
||||
page_title: packer fix - Commands
|
||||
sidebar_title: <tt>fix</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The `packer fmt` Packer command is used to format HCL2
|
||||
configuration files to a canonical format and style.
|
||||
layout: docs
|
||||
page_title: packer fmt - Commands
|
||||
sidebar_title: <tt>fmt</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ description: |
|
|||
The `packer hcl2_upgrade` Packer command is used to transpile a JSON
|
||||
configuration template to it's formatted HCL2 counterpart. The command will
|
||||
return a zero exit status on success, and a non-zero exit status on failure.
|
||||
layout: docs
|
||||
page_title: packer hcl2_upgrade - Commands
|
||||
sidebar_title: <tt>hcl2_upgrade</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -5,7 +5,6 @@ description: |
|
|||
`packer` tool takes a subcommand to execute, and that subcommand may have
|
||||
additional options as well. Subcommands are executed with `packer SUBCOMMAND`,
|
||||
where "SUBCOMMAND" is the actual command you wish to execute.
|
||||
layout: docs
|
||||
page_title: Commands
|
||||
sidebar_title: Commands (CLI)
|
||||
---
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ description: >
|
|||
like what variables a template accepts, the builders it defines, the
|
||||
|
||||
provisioners it defines and the order they'll run, and more.
|
||||
layout: docs
|
||||
page_title: packer inspect - Commands
|
||||
sidebar_title: <tt>inspect</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: |
|
|||
configuration of a template. The command will return a zero exit status on
|
||||
success, and a non-zero exit status on failure. Additionally, if a template
|
||||
doesn't validate, any error messages will be outputted.
|
||||
layout: docs
|
||||
page_title: packer validate - Commands
|
||||
sidebar_title: <tt>validate</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
Communicators are the mechanism Packer uses to upload files, execute
|
||||
scripts, etc. with the machine being created.
|
||||
layout: docs
|
||||
page_title: Communicators
|
||||
sidebar_title: Communicators
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
The SSH communicator uses SSH to upload files, execute scripts, etc. on
|
||||
the machine being created.
|
||||
layout: docs
|
||||
page_title: Communicators - SSH
|
||||
sidebar_title: SSH
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
Communicators are the mechanism Packer uses to upload files, execute scripts,
|
||||
etc. with the machine being created.
|
||||
layout: docs
|
||||
page_title: Communicators - Templates
|
||||
sidebar_title: WINRM
|
||||
---
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ description: >
|
|||
you generally don't have to worry about it until you want to tweak a
|
||||
|
||||
configuration.
|
||||
layout: docs
|
||||
page_title: Core Configuration - Other
|
||||
sidebar_title: Core Configuration
|
||||
---
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ description: |
|
|||
Packer strives to be stable and bug-free, but issues inevitably arise where
|
||||
certain things may not work entirely correctly, or may not appear to work
|
||||
correctly.
|
||||
layout: docs
|
||||
page_title: Debugging - Other
|
||||
sidebar_title: Debugging
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,6 +1,5 @@
|
|||
---
|
||||
description: Packer uses a variety of environmental variables.
|
||||
layout: docs
|
||||
page_title: Environment Variables - Other
|
||||
sidebar_title: Environment Variables
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: |
|
||||
It is possible to write custom builders using the Packer plugin interface, and
|
||||
this page documents how to do that.
|
||||
layout: docs
|
||||
page_title: Custom Builders - Extending
|
||||
sidebar_title: Custom Builders
|
||||
---
|
||||
|
|
|
|||
|
|
@ -4,7 +4,6 @@ description: >
|
|||
artifact
|
||||
|
||||
into another, for example by compressing files, or uploading them.
|
||||
layout: docs
|
||||
page_title: Custom Post-Processors - Extending
|
||||
sidebar_title: Custom Post-Processors
|
||||
---
|
||||
|
|
|
|||
|
|
@ -8,7 +8,6 @@ description: >
|
|||
example of a provisioner is the shell provisioner, which runs shell scripts
|
||||
|
||||
within the machines.
|
||||
layout: docs
|
||||
page_title: Custom Provisioners - Extending
|
||||
sidebar_title: Custom Provisioners
|
||||
---
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ description: |
|
|||
Packer is designed to be extensible. Because the surface area for workloads is
|
||||
infinite, Packer supports plugins for builders, provisioners, and
|
||||
post-processors.
|
||||
layout: docs
|
||||
page_title: Extending
|
||||
sidebar_title: Extending Packer
|
||||
---
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ description: |
|
|||
Packer Plugins allow new functionality to be added to Packer without modifying
|
||||
the core source code. Packer plugins are able to add new builders,
|
||||
provisioners, hooks, and more.
|
||||
layout: docs
|
||||
page_title: Plugins - Extending
|
||||
sidebar_title: Plugins
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
description: >
|
||||
description: |
|
||||
The source block defines what builders are started.
|
||||
layout: docs
|
||||
page_title: build - Blocks
|
||||
sidebar_title: <tt>build</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
description: >
|
||||
description: |
|
||||
The post-processor block defines how a post-processor is configured.
|
||||
layout: docs
|
||||
page_title: post-processor - build - Blocks
|
||||
sidebar_title: <tt>post-processor</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: >
|
||||
The post-processors block allows to define lists of post-processors to apply
|
||||
to an artifact.
|
||||
layout: docs
|
||||
page_title: post-processors - build - Blocks
|
||||
sidebar_title: <tt>post-processors</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
description: >
|
||||
description: |
|
||||
The provisioner block defines how a provisioner is configured.
|
||||
layout: docs
|
||||
page_title: provisioner - build - Blocks
|
||||
sidebar_title: <tt>provisioner</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: >
|
||||
A source block nested in a build block allows you to use an already defined
|
||||
source and to set specific fields.
|
||||
layout: docs
|
||||
page_title: source - build - Blocks
|
||||
sidebar_title: <tt>source</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,9 +1,7 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Blocks - Configuration Language
|
||||
sidebar_title: Blocks
|
||||
description: |-
|
||||
The HCL language has a number of blocks that can be used to configure builds.
|
||||
description: The HCL language has a number of blocks that can be used to configure builds.
|
||||
---
|
||||
|
||||
# Built-in Blocks
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: >
|
||||
The locals block also called the local-variable block defines locals within
|
||||
your Packer configuration.
|
||||
layout: docs
|
||||
page_title: locals - Blocks
|
||||
sidebar_title: <tt>locals</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,5 +1,4 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: packer - Blocks
|
||||
sidebar_title: <tt>packer</tt>
|
||||
description: |-
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
---
|
||||
description: >
|
||||
description: |
|
||||
The top-level source block defines reusable builder configuration blocks
|
||||
layout: docs
|
||||
page_title: source - Blocks
|
||||
sidebar_title: <tt>source</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -2,7 +2,6 @@
|
|||
description: >
|
||||
The variable block, also called the input-variable block, defines variables
|
||||
within your Packer configuration.
|
||||
layout: docs
|
||||
page_title: variable - Blocks
|
||||
sidebar_title: <tt>variable</tt>
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,9 +1,10 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Contextual Variables - HCL Configuration Language
|
||||
sidebar_title: Contextual Variables
|
||||
description: |-
|
||||
Special variables provide connection information and basic instance state information.
|
||||
description: >-
|
||||
Special variables provide connection information and basic instance state
|
||||
information.
|
||||
|
||||
This page covers all existing special variables.
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,4 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Expressions - Configuration Language
|
||||
sidebar_title: Expressions
|
||||
description: |-
|
||||
|
|
|
|||
|
|
@ -1,5 +1,4 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: chunklist - Functions - Configuration Language
|
||||
sidebar_title: chunklist
|
||||
description: |-
|
||||
|
|
|
|||
|
|
@ -1,5 +1,4 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: coalesce - Functions - Configuration Language
|
||||
sidebar_title: coalesce
|
||||
description: |-
|
||||
|
|
|
|||
|
|
@ -1,5 +1,4 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: coalescelist - Functions - Configuration Language
|
||||
sidebar_title: coalescelist
|
||||
description: |-
|
||||
|
|
|
|||
|
|
@ -1,5 +1,4 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: compact - Functions - Configuration Language
|
||||
sidebar_title: compact
|
||||
description: The compact function removes empty string elements from a list.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,4 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: concat - Functions - Configuration Language
|
||||
sidebar_title: concat
|
||||
description: The concat function combines two or more lists into a single list.
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue