From 651fe263818d1c4ad5ba8adf8c8485ce647dc40b Mon Sep 17 00:00:00 2001 From: Thomas Hipp Date: Fri, 15 Sep 2017 09:37:45 +0200 Subject: vendor: update deps This updates all vendored packages. The Glide config has been changed to try and stick to versions instead of commit IDs if possible. Signed-off-by: Thomas Hipp --- .../github.com/mitchellh/packer/website/config.rb | 8 +- .../source/docs/builders/alicloud-ecs.html.md | 1 + .../source/docs/builders/amazon-chroot.html.md | 17 ++- .../source/docs/builders/amazon-ebs.html.md | 17 ++- .../docs/builders/amazon-ebssurrogate.html.md | 17 ++- .../source/docs/builders/amazon-ebsvolume.html.md | 17 ++- .../source/docs/builders/amazon-instance.html.md | 17 ++- .../website/source/docs/builders/azure.html.md | 16 ++- .../source/docs/builders/cloudstack.html.md | 12 ++ .../website/source/docs/builders/docker.html.md | 4 + .../source/docs/builders/googlecompute.html.md | 9 ++ .../website/source/docs/builders/lxc.html.md | 97 ++++++++++++++ .../website/source/docs/builders/lxd.html.md | 52 ++++++++ .../source/docs/builders/oracle-oci.html.md | 143 +++++++++++++++++++++ .../source/docs/builders/vmware-iso.html.md | 3 +- .../docs/post-processors/vsphere-template.html.md | 53 ++++++++ .../source/docs/provisioners/ansible-local.html.md | 3 + .../source/docs/provisioners/ansible.html.md | 24 ++++ .../docs/provisioners/puppet-masterless.html.md | 50 ++++--- .../source/docs/provisioners/puppet-server.html.md | 44 +++++-- .../source/docs/templates/communicator.html.md | 4 +- .../intro/getting-started/build-image.html.md | 2 +- .../source/intro/getting-started/next.html.md | 4 - .../intro/getting-started/remote-builds.html.md | 112 ---------------- .../source/intro/hashicorp-ecosystem.html.md | 68 ---------- .../packer/website/source/layouts/docs.erb | 11 +- .../packer/website/source/layouts/intro.erb | 6 - 27 files changed, 549 insertions(+), 262 deletions(-) create mode 100644 vendor/github.com/mitchellh/packer/website/source/docs/builders/lxc.html.md create mode 100644 vendor/github.com/mitchellh/packer/website/source/docs/builders/lxd.html.md create mode 100644 vendor/github.com/mitchellh/packer/website/source/docs/builders/oracle-oci.html.md create mode 100644 vendor/github.com/mitchellh/packer/website/source/docs/post-processors/vsphere-template.html.md delete mode 100644 vendor/github.com/mitchellh/packer/website/source/intro/getting-started/remote-builds.html.md delete mode 100644 vendor/github.com/mitchellh/packer/website/source/intro/hashicorp-ecosystem.html.md (limited to 'vendor/github.com/mitchellh/packer/website') diff --git a/vendor/github.com/mitchellh/packer/website/config.rb b/vendor/github.com/mitchellh/packer/website/config.rb index 482309b3..faa4bf65 100644 --- a/vendor/github.com/mitchellh/packer/website/config.rb +++ b/vendor/github.com/mitchellh/packer/website/config.rb @@ -2,7 +2,7 @@ set :base_url, "https://www.packer.io/" activate :hashicorp do |h| h.name = "packer" - h.version = "1.0.3" + h.version = "1.1.0" h.github_slug = "hashicorp/packer" h.website_root = "website" end @@ -27,8 +27,8 @@ helpers do return "#{page.data.page_title} - Packer by HashiCorp" end - "Packer by HashiCorp" - end + "Packer by HashiCorp" + end # Get the description for the page # @@ -81,7 +81,7 @@ helpers do def body_classes_for(page) classes = [] - if !(layout = page.data.layout).blank? + if !(page.data.layout).blank? classes << "layout-#{page.data.layout}" end diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/alicloud-ecs.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/alicloud-ecs.html.md index 6db22f4f..614b2d3d 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/alicloud-ecs.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/alicloud-ecs.html.md @@ -4,6 +4,7 @@ description: | customized images based on an existing base images. layout: docs page_title: Alicloud Image Builder +sidebar_current: 'docs-builders-alicloud-ecs' --- # Alicloud Image Builder diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-chroot.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-chroot.html.md index 36c0cde1..d1ba50d8 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-chroot.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-chroot.html.md @@ -128,11 +128,10 @@ each category, the available configuration keys are alphabetized. source AMI will be attached. This defaults to "" (empty string), which forces Packer to find an open device automatically. -- `enhanced_networking` (boolean) - Enable enhanced - networking (SriovNetSupport and ENA) on HVM-compatible AMIs. If true, add - `ec2:ModifyInstanceAttribute` to your AWS IAM policy. Note: you must make - sure enhanced networking is enabled on your instance. See [Amazon's - documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking) +- `ena_support` (boolean) - Enable enhanced networking (ENA but not SriovNetSupport) + on HVM-compatible AMIs. If true, add `ec2:ModifyInstanceAttribute` to your AWS IAM policy. + Note: you must make sure enhanced networking is enabled on your instance. See [Amazon's + documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking). Default `false`. - `force_deregister` (boolean) - Force Packer to first deregister an existing AMI if one with the same name already exists. Default `false`. @@ -270,7 +269,7 @@ each category, the available configuration keys are alphabetized. "source_ami_filter": { "filters": { "virtualization-type": "hvm", - "name": "*ubuntu-xenial-16.04-amd64-server-*", + "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*", "root-device-type": "ebs" }, "owners": ["099720109477"], @@ -293,6 +292,12 @@ each category, the available configuration keys are alphabetized. - `most_recent` (bool) - Selects the newest created image when true. This is most useful for selecting a daily distro build. +- `sriov_support` (boolean) - Enable enhanced networking (SriovNetSupport but not ENA) + on HVM-compatible AMIs. If true, add `ec2:ModifyInstanceAttribute` to your AWS IAM + policy. Note: you must make sure enhanced networking is enabled on your instance. See [Amazon's + documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking). + Default `false`. + - `tags` (object of key/value strings) - Tags applied to the AMI. This is a [template engine](/docs/templates/engine.html) where the `SourceAMI` variable is replaced with the source AMI ID and diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebs.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebs.html.md index 0bdb3021..f144fbba 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebs.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebs.html.md @@ -165,11 +165,10 @@ builder. Optimized](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html). Default `false`. -- `enhanced_networking` (boolean) - Enable enhanced - networking (SriovNetSupport and ENA) on HVM-compatible AMIs. If true, add - `ec2:ModifyInstanceAttribute` to your AWS IAM policy. Note: you must make - sure enhanced networking is enabled on your instance. See [Amazon's - documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking) +- `ena_support` (boolean) - Enable enhanced networking (ENA but not SriovNetSupport) + on HVM-compatible AMIs. If true, add `ec2:ModifyInstanceAttribute` to your AWS IAM policy. + Note: you must make sure enhanced networking is enabled on your instance. See [Amazon's + documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking). Default `false`. - `force_deregister` (boolean) - Force Packer to first deregister an existing AMI if one with the same name already exists. Default `false`. @@ -265,7 +264,7 @@ builder. "source_ami_filter": { "filters": { "virtualization-type": "hvm", - "name": "*ubuntu-xenial-16.04-amd64-server-*", + "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*", "root-device-type": "ebs" }, "owners": ["099720109477"], @@ -302,6 +301,12 @@ builder. best spot price. This must be one of: `Linux/UNIX`, `SUSE Linux`, `Windows`, `Linux/UNIX (Amazon VPC)`, `SUSE Linux (Amazon VPC)`, `Windows (Amazon VPC)` +- `sriov_support` (boolean) - Enable enhanced networking (SriovNetSupport but not ENA) + on HVM-compatible AMIs. If true, add `ec2:ModifyInstanceAttribute` to your AWS IAM + policy. Note: you must make sure enhanced networking is enabled on your instance. See [Amazon's + documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking). + Default `false`. + - `ssh_keypair_name` (string) - If specified, this is the key that will be used for SSH with the machine. The key must match a key pair name loaded up into Amazon EC2. By default, this is blank, and Packer will diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebssurrogate.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebssurrogate.html.md index 071af814..f60f6de1 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebssurrogate.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebssurrogate.html.md @@ -158,11 +158,10 @@ builder. Optimized](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html). Default `false`. -- `enhanced_networking` (boolean) - Enable enhanced - networking (SriovNetSupport and ENA) on HVM-compatible AMIs. If true, add - `ec2:ModifyInstanceAttribute` to your AWS IAM policy. Note: you must make - sure enhanced networking is enabled on your instance. See [Amazon's - documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking) +- `ena_support` (boolean) - Enable enhanced networking (ENA but not SriovNetSupport) + on HVM-compatible AMIs. If true, add `ec2:ModifyInstanceAttribute` to your AWS IAM policy. + Note: you must make sure enhanced networking is enabled on your instance. See [Amazon's + documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking). Default `false`. - `force_deregister` (boolean) - Force Packer to first deregister an existing AMI if one with the same name already exists. Default `false`. @@ -258,7 +257,7 @@ builder. "source_ami_filter": { "filters": { "virtualization-type": "hvm", - "name": "*ubuntu-xenial-16.04-amd64-server-*", + "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*", "root-device-type": "ebs" }, "owners": ["099720109477"], @@ -295,6 +294,12 @@ builder. best spot price. This must be one of: `Linux/UNIX`, `SUSE Linux`, `Windows`, `Linux/UNIX (Amazon VPC)`, `SUSE Linux (Amazon VPC)`, `Windows (Amazon VPC)` +- `sriov_support` (boolean) - Enable enhanced networking (SriovNetSupport but not ENA) + on HVM-compatible AMIs. If true, add `ec2:ModifyInstanceAttribute` to your AWS IAM + policy. Note: you must make sure enhanced networking is enabled on your instance. See [Amazon's + documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking). + Default `false`. + - `ssh_keypair_name` (string) - If specified, this is the key that will be used for SSH with the machine. The key must match a key pair name loaded up into Amazon EC2. By default, this is blank, and Packer will diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebsvolume.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebsvolume.html.md index c27c5414..06da8399 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebsvolume.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-ebsvolume.html.md @@ -104,11 +104,10 @@ builder. Optimized](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html). Default `false`. -- `enhanced_networking` (boolean) - Enable enhanced - networking (SriovNetSupport and ENA) on HVM-compatible AMIs. If true, add - `ec2:ModifyInstanceAttribute` to your AWS IAM policy. Note: you must make - sure enhanced networking is enabled on your instance. See [Amazon's - documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking) +- `ena_support` (boolean) - Enable enhanced networking (ENA but not SriovNetSupport) + on HVM-compatible AMIs. If true, add `ec2:ModifyInstanceAttribute` to your AWS IAM policy. + Note: you must make sure enhanced networking is enabled on your instance. See [Amazon's + documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking). Default `false`. - `iam_instance_profile` (string) - The name of an [IAM instance profile](https://docs.aws.amazon.com/IAM/latest/UserGuide/instance-profiles.html) @@ -171,7 +170,7 @@ builder. "source_ami_filter": { "filters": { "virtualization-type": "hvm", - "name": "*ubuntu-xenial-16.04-amd64-server-*", + "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*", "root-device-type": "ebs" }, "owners": ["099720109477"], @@ -208,6 +207,12 @@ builder. best spot price. This must be one of: `Linux/UNIX`, `SUSE Linux`, `Windows`, `Linux/UNIX (Amazon VPC)`, `SUSE Linux (Amazon VPC)` or `Windows (Amazon VPC)` +- `sriov_support` (boolean) - Enable enhanced networking (SriovNetSupport but not ENA) + on HVM-compatible AMIs. If true, add `ec2:ModifyInstanceAttribute` to your AWS IAM + policy. Note: you must make sure enhanced networking is enabled on your instance. See [Amazon's + documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking). + Default `false`. + - `ssh_keypair_name` (string) - If specified, this is the key that will be used for SSH with the machine. By default, this is blank, and Packer will generate a temporary key pair unless diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-instance.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-instance.html.md index c63e537a..8bbd72b8 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-instance.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/amazon-instance.html.md @@ -189,11 +189,10 @@ builder. Optimized](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html). Default `false`. -- `enhanced_networking` (boolean) - Enable enhanced - networking (SriovNetSupport and ENA) on HVM-compatible AMIs. If true, add - `ec2:ModifyInstanceAttribute` to your AWS IAM policy. Note: you must make - sure enhanced networking is enabled on your instance. See [Amazon's - documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking) +- `ena_support` (boolean) - Enable enhanced networking (ENA but not SriovNetSupport) + on HVM-compatible AMIs. If true, add `ec2:ModifyInstanceAttribute` to your AWS IAM policy. + Note: you must make sure enhanced networking is enabled on your instance. See [Amazon's + documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking). Default `false`. - `force_deregister` (boolean) - Force Packer to first deregister an existing AMI if one with the same name already exists. Defaults to `false`. @@ -263,7 +262,7 @@ builder. "source_ami_filter": { "filters": { "virtualization-type": "hvm", - "name": "*ubuntu-xenial-16.04-amd64-server-*", + "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*", "root-device-type": "ebs" }, "owners": ["099720109477"], @@ -303,6 +302,12 @@ builder. best spot price. This must be one of: `Linux/UNIX`, `SUSE Linux`, `Windows`, `Linux/UNIX (Amazon VPC)`, `SUSE Linux (Amazon VPC)`, `Windows (Amazon VPC)` +- `sriov_support` (boolean) - Enable enhanced networking (SriovNetSupport but not ENA) + on HVM-compatible AMIs. If true, add `ec2:ModifyInstanceAttribute` to your AWS IAM + policy. Note: you must make sure enhanced networking is enabled on your instance. See [Amazon's + documentation on enabling enhanced networking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking). + Default `false`. + - `ssh_keypair_name` (string) - If specified, this is the key that will be used for SSH with the machine. The key must match a key pair name loaded up into Amazon EC2. By default, this is blank, and Packer will diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/azure.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/azure.html.md index ec391631..abda2a5f 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/azure.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/azure.html.md @@ -50,7 +50,10 @@ builder. #### VHD or Managed Image -The Azure builder can create either a VHD, or a managed image. When creating a VHD the following two options are required. +The Azure builder can create either a VHD, or a managed image. If you +are creating a VHD, you **must** start with a VHD. Likewise, if you +want to create a managed image you **must** start with a managed +image. When creating a VHD the following two options are required. - `capture_container_name` (string) Destination container name. Essentially the "directory" where your VHD will be organized in Azure. The captured VHD's URL will be https://.blob.core.windows.net/system/Microsoft.Compute/Images//.xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.vhd. @@ -107,6 +110,10 @@ When creating a managed image the following two options are required. - `image_url` (string) Specify a custom VHD to use. If this value is set, do not set image\_publisher, image\_offer, image\_sku, or image\_version. + +- `managed_image_storage_account_type` (string) Specify the storage + account type for a managed image. Valid values are Standard_LRS + and Premium\_LRS. The default is Standard\_LRS. - `object_id` (string) Specify an OAuth Object ID to protect WinRM certificates created at runtime. This variable is required when creating images based on @@ -131,9 +138,12 @@ When creating a managed image the following two options are required. - `tenant_id` (string) The account identifier with which your `client_id` and `subscription_id` are associated. If not specified, `tenant_id` will be looked up using `subscription_id`. +- `private_virtual_network_with_public_ip` (boolean) This value allows you to set a `virtual_network_name` and obtain + a public IP. If this value is not set and `virtual_network_name` is defined Packer is only allowed to be executed + from a host on the same subnet / virtual network. + - `virtual_network_name` (string) Use a pre-existing virtual network for the VM. This option enables private - communication with the VM, no public IP address is **used** or **provisioned**. This value should only be set if - Packer is executed from a host on the same subnet / virtual network. + communication with the VM, no public IP address is **used** or **provisioned** (unless you set `private_virtual_network_with_public_ip`). - `virtual_network_resource_group_name` (string) If virtual\_network\_name is set, this value **may** also be set. If virtual\_network\_name is set, and this value is not set the builder attempts to determine the resource group diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/cloudstack.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/cloudstack.html.md index 9b6bc2ca..7e59fe71 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/cloudstack.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/cloudstack.html.md @@ -74,6 +74,11 @@ builder. connect to the instance. Defaults to `[ "0.0.0.0/0" ]`. Only required when `use_local_ip_address` is `false`. +- `create_security_group` (boolean) - If `true` a temporary security group + will be created which allows traffic towards the instance from the + `cidr_list`. This option will be ignored if `security_groups` is also + defined. Requires `expunge` set to `true`. Defaults to `false`. + - `disk_offering` (string) - The name or ID of the disk offering used for the instance. This option is only available (and also required) when using `source_iso`. @@ -118,6 +123,9 @@ builder. connecting any provisioners to. If not provided, a temporary public IP address will be associated and released during the Packer run. +- `security_groups` (array of strings) - A list of security group IDs or names + to associate the instance with. + - `ssh_agent_auth` (boolean) - If true, the local SSH agent will be used to authenticate connections to the source instance. No temporary keypair will be created, and the values of `ssh_password` and `ssh_private_key_file` will @@ -149,6 +157,10 @@ builder. - `template_scalable` (boolean) - Set to `true` to indicate that the template contains tools to support dynamic scaling of VM cpu/memory. Defaults to `false`. +- `temporary_keypair_name` (string) - The name of the temporary SSH key pair + to generate. By default, Packer generates a name that looks like + `packer_`, where <UUID> is a 36 character unique identifier. + - `user_data` (string) - User data to launch with the instance. This is a [template engine](/docs/templates/engine.html) see _User Data_ bellow for more details. diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/docker.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/docker.html.md index c8276540..7fab6d09 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/docker.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/docker.html.md @@ -204,6 +204,10 @@ You must specify (only) one of `commit`, `discard`, or `export_path`. mount into this container. The key of the object is the host path, the value is the container path. +- `container_dir` (string) - The directory inside container to mount + temp directory from host server for work [file provisioner](/docs/provisioners/file.html). + By default this is set to `/packer-files`. + ## Using the Artifact: Export Once the tar artifact has been generated, you will likely want to import, tag, diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/googlecompute.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/googlecompute.html.md index cce0e41c..dda8841d 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/googlecompute.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/googlecompute.html.md @@ -174,6 +174,12 @@ builder. Not required if you run Packer on a GCE instance with a service account. Instructions for creating file or using service accounts are above. +- `accelerator_count` (int) - Number of guest accelerator cards to add to the launched instance. + +- `accelerator_type` (string) - Full or partial URL of the guest accelerator type. GPU accelerators can only be used with + `"on_host_maintenance": "TERMINATE"` option set. + Example: `"projects/project_id/zones/europe-west1-b/acceleratorTypes/nvidia-tesla-k80"` + - `address` (string) - The name of a pre-allocated static external IP address. Note, must be the name and not the actual IP address. @@ -198,6 +204,9 @@ builder. - `instance_name` (string) - A name to give the launched instance. Beware that this must be unique. Defaults to `"packer-{{uuid}}"`. +- `labels` (object of key/value strings) - Key/value pair labels to apply to + the launched instance. + - `machine_type` (string) - The machine type. Defaults to `"n1-standard-1"`. - `metadata` (object of key/value strings) - Metadata applied to the launched diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/lxc.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/lxc.html.md new file mode 100644 index 00000000..0dc207a9 --- /dev/null +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/lxc.html.md @@ -0,0 +1,97 @@ +--- +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 Builder +... + +# LXC Builder + +Type: `lxc` + +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. + +The LXC builder requires a modern linux kernel and the `lxc` or `lxc1` package. +This builder does not work with LXD. + +Note to build Centos images on a Debian family host, you will need the `yum` package installed. + +Some provisioners such as `ansible-local` get confused when running in a container of a different family. +E.G. it will attempt to use `apt-get` to install packages, when running in a Centos container if the parent OS is Debian based. + +## Basic Example + +Below is a fully functioning example. + +``` {.javascript} +{ + "builders": [ + { + "type": "lxc", + "name": "lxc-trusty", + "config_file": "/tmp/lxc/config", + "template_name": "ubuntu", + "template_environment_vars": [ + "SUITE=trusty" + ] + }, + { + "type": "lxc", + "name": "lxc-xenial", + "config_file": "/tmp/lxc/config", + "template_name": "ubuntu", + "template_environment_vars": [ + "SUITE=xenial" + ] + }, + { + "type": "lxc", + "name": "lxc-jessie", + "config_file": "/tmp/lxc/config", + "template_name": "debian", + "template_environment_vars": [ + "SUITE=jessie" + ] + }, + { + "type": "lxc", + "name": "lxc-centos-7-x64", + "config_file": "/tmp/lxc/config", + "template_name": "centos", + "template_parameters": [ + "-R","7", + "-a","x86_64" + ] + } + ] +} +``` + +## Configuration Reference + +### Required: + +- `config_file` (string) - The path to the lxc configuration file. + +- `template_name` (string) - The LXC template name to use. + +- `template_environment_vars` (array of strings) - Environmental variables to use to build the template with. + +### Optional: + +- `target_runlevel` (int) - The minimum run level to wait for the container to reach. Note some distributions (Ubuntu) simulate run levels and may report 5 rather than 3. + +- `output_directory` (string) - The directory in which to save the exported tar.gz. Defaults to `output-` in the current directory. + +- `container_name` (string) - The name of the LXC container. Usually stored in `/var/lib/lxc/containers/`. Defaults to `packer-`. + +- `command_wrapper` (string) - Allows you to specify a wrapper command, such as `ssh` so you can execute packer builds on a remote host. Defaults to Empty. + +- `init_timeout` (string) - The timeout in seconds to wait for the the container to start. Defaults to 20 seconds. + +- `template_parameters` (array of strings) - Options to pass to the given `lxc-template` command, usually located in `/usr/share/lxc/templates/lxc-``. Note: This gets passed as ARGV to the template command. Ensure you have an array of strings, as a single string with spaces probably won't work. Defaults to `[]`. + diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/lxd.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/lxd.html.md new file mode 100644 index 00000000..dd386b1b --- /dev/null +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/lxd.html.md @@ -0,0 +1,52 @@ +--- +description: | + The `lxd` Packer builder builds containers for LXD. The builder starts an LXD + container, runs provisioners within this container, then saves the container + as an LXD image. +layout: docs +page_title: LXD Builder +... + +# LXD Builder + +Type: `lxd` + +The `lxd` Packer builder builds containers for LXD. The builder starts an LXD +container, runs provisioners within this container, then saves the container +as an LXD image. + +The LXD builder requires a modern linux kernel and the `lxd` package. +This builder does not work with LXC. + +## Basic Example + +Below is a fully functioning example. + +``` {.javascript} +{ + "builders": [ + { + "type": "lxd", + "name": "lxd-xenial", + "image": "ubuntu-daily:xenial", + "output_image": "ubuntu-xenial" + } + ] +} +``` + +## Configuration Reference + +### Required: + +- `image` (string) - The source image to use when creating the build container. This can be a (local or remote) image (name or fingerprint). E.G. my-base-image, ubuntu-daily:x, 08fababf6f27... + Note: The builder may appear to pause if required to download a remote image, as they are usually 100-200MB. `/var/log/lxd/lxd.log` will mention starting such downloads. + +### Optional: + +- `name` (string) - The name of the started container. Defaults to `packer-$PACKER_BUILD_NAME`. + +- `output_image` (string) - The name of the output artifact. Defaults to `name`. + +- `command_wrapper` (string) - lets you prefix all builder commands, such as with `ssh` for a remote build host. Defaults to `""`. + diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/oracle-oci.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/oracle-oci.html.md new file mode 100644 index 00000000..3503d4fc --- /dev/null +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/oracle-oci.html.md @@ -0,0 +1,143 @@ +--- +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_current: 'docs-builders-oracle-oci' +--- + +# Oracle Cloud Infrastructure (OCI) Builder + +Type: `oracle-oci` + +The `oracle-oci` Packer builder is able to create new custom images for use +with [Oracle Cloud Infrastructure](https://cloud.oracle.com) (OCI). The builder +takes a base image, runs any provisioning necessary on the base image after +launching it, and finally snapshots it creating a reusable custom image. + +It is recommended that you familiarise yourself with the +[Key Concepts and Terminology](https://docs.us-phoenix-1.oraclecloud.com/Content/GSG/Concepts/concepts.htm) +prior to using this builder if you have not done so already. + +The builder _does not_ manage images. Once it creates an image, it is up to you +to use it or delete it. + +## Authorization + +The Oracle OCI API requires that requests be signed with the RSA public key +associated with your [IAM](https://docs.us-phoenix-1.oraclecloud.com/Content/Identity/Concepts/overview.htm) +user account. For a comprehensive example of how to configure the required +authentication see the documentation on +[Required Keys and OCIDs](https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm) +([Oracle Cloud IDs](https://docs.us-phoenix-1.oraclecloud.com/Content/General/Concepts/identifiers.htm)). + +## Configuration Reference + +There are many configuration options available for the `oracle-oci` builder. +In addition to the options listed here, a +[communicator](/docs/templates/communicator.html) can be configured for this +builder. + +### Required + + - `availability_domain` (string) - The name of the + [Availability Domain](https://docs.us-phoenix-1.oraclecloud.com/Content/General/Concepts/regions.htm) + within which a new instance is launched and provisioned. + The names of the Availability Domains have a prefix that is specific to + your [tenancy](https://docs.us-phoenix-1.oraclecloud.com/Content/GSG/Concepts/concepts.htm#two). + + To get a list of the Availability Domains, use the + [ListAvailabilityDomains](https://docs.us-phoenix-1.oraclecloud.com/api/#/en/identity/latest/AvailabilityDomain/ListAvailabilityDomains) + operation, which is available in the IAM Service API. + + - `base_image_ocid` (string) - The OCID of the [base image](https://docs.us-phoenix-1.oraclecloud.com/Content/Compute/References/images.htm) + to use. This is the unique identifier of the image that will be used to + launch a new instance and provision it. + + To get a list of the accepted image OCIDs, use the + [ListImages](https://docs.us-phoenix-1.oraclecloud.com/api/#/en/iaas/latest/Image/ListImages) + operation available in the Core Services API. + + - `compartment_ocid` (string) - The OCID of the + [compartment](https://docs.us-phoenix-1.oraclecloud.com/Content/GSG/Tasks/choosingcompartments.htm) + + - `fingerprint` (string) - Fingerprint for the OCI API signing key. + Overrides value provided by the + [OCI config file](https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/sdkconfig.htm) + if present. + + - `shape` (string) - The template that determines the number of + CPUs, amount of memory, and other resources allocated to a newly created + instance. + + To get a list of the available shapes, use the + [ListShapes](https://docs.us-phoenix-1.oraclecloud.com/api/#/en/iaas/20160918/Shape/ListShapes) + operation available in the Core Services API. + + - `subnet_ocid` (string) - The name of the subnet within which a new instance + is launched and provisioned. + + To get a list of your subnets, use the + [ListSubnets](https://docs.us-phoenix-1.oraclecloud.com/api/#/en/iaas/latest/Subnet/ListSubnets) + operation available in the Core Services API. + + Note: the subnet must be configured to allow access via your chosen + [communicator](/docs/templates/communicator.html) (communicator defaults to + [SSH tcp/22](/docs/templates/communicator.html#ssh_port)). + + +### Optional + + - `access_cfg_file` (string) - The path to the + [OCI config file](https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/sdkconfig.htm). + Defaults to `$HOME/.oci/config`. + + - `access_cfg_file_account` (string) - The specific account in the + [OCI config file](https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/sdkconfig.htm) + to use. Defaults to `DEFAULT`. + + - `image_name` (string) - The name to assign to the resulting custom image. + + - `key_file` (string) - Full path and filename of the OCI API signing key. + Overrides value provided by the + [OCI config file](https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/sdkconfig.htm) + if present. + + - `pass_phrase` (string) - Pass phrase used to decrypt the OCI API signing + key. Overrides value provided by the + [OCI config file](https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/sdkconfig.htm) + if present. + + - `region` (string) - An Oracle Cloud Infrastructure region. Overrides + value provided by the + [OCI config file](https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/sdkconfig.htm) + if present. + + - `tenancy_ocid` (string) - The OCID of your tenancy. Overrides value provided + by the + [OCI config file](https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/sdkconfig.htm) + if present. + + - `user_ocid` (string) - The OCID of the user calling the OCI API. Overrides + value provided by the [OCI config file](https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/sdkconfig.htm) + if present. + + +## Basic Example + +Here is a basic example. Note that account specific configuration has been +substituted with the letter `a` and OCIDS have been shortened for brevity. + +``` {.json} +{ + "availability_domain": "aaaa:PHX-AD-1", + "base_image_ocid": "ocid1.image.oc1.phx.aaaaaaaa5yu6pw3riqtuhxzov7fdngi4tsteganmao54nq3pyxu3hxcuzmoa", + "compartment_ocid": "ocid1.compartment.oc1..aaa", + "image_name": "ExampleImage", + "shape": "VM.Standard1.1", + "ssh_username": "opc", + "subnet_ocid": "ocid1.subnet.oc1..aaa", + "type": "oracle-oci" +} +``` diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/builders/vmware-iso.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/builders/vmware-iso.html.md index 478c1a0b..4d00965b 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/builders/vmware-iso.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/builders/vmware-iso.html.md @@ -478,7 +478,8 @@ modify as well: - `format` (string) - Either "ovf", "ova" or "vmx", this specifies the output format of the exported virtual machine. This defaults to "ovf". - Before using this option, you need to install `ovftool`. + Before using this option, you need to install `ovftool`. This option + works currently only with option remote_type set to "esx5". ### VNC port discovery diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/post-processors/vsphere-template.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/post-processors/vsphere-template.html.md new file mode 100644 index 00000000..e72dc19c --- /dev/null +++ b/vendor/github.com/mitchellh/packer/website/source/docs/post-processors/vsphere-template.html.md @@ -0,0 +1,53 @@ +--- +description: | + The Packer vSphere Template post-processor takes an artifact from the VMware-iso builder built on ESXi (i.e. remote) + and allows to mark a VM as a template and leaving it in a path of choice. +layout: docs +page_title: 'vSphere Template - Post-Processors' +sidebar_current: 'docs-post-processors-vSphere-template' +--- + +# vSphere Template Post-Processor + +Type: `vsphere-template` + +The Packer vSphere template post-processor takes an artifact from the VMware-iso builder built on ESXi (i.e. remote) and +allows to mark a VM as a template and leaving it in a path of choice. + +## Example + +An example is shown below, showing only the post-processor configuration: + +``` json +{ + "type": "vsphere-template", + "host": "vcenter.local", + "insecure": true, + "username": "root", + "password": "secret", + "datacenter": "mydatacenter", + "folder": "/packer-templates/os/distro-7" +} +``` + +## Configuration + +There are many configuration options available for the post-processor. They are +segmented below into two categories: required and optional parameters. Within +each category, the available configuration keys are alphabetized. + +Required: + +- `host` (string) - The vSphere host that contains the VM built by the vmware-iso. + +- `password` (string) - Password to use to authenticate to the vSphere endpoint. + +- `username` (string) - The username to use to authenticate to the vSphere endpoint. + +Optional: + +- `datacenter` (string) - If you have more than one, you will need to specify which one the ESXi used. + +- `folder` (string) - Target path where the template will be created. + +- `insecure` (boolean) - If it's true skip verification of server certificate. Default is false diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/ansible-local.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/ansible-local.html.md index 3ca775cf..f2160792 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/ansible-local.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/ansible-local.html.md @@ -114,6 +114,9 @@ chi-appservers cli](http://docs.ansible.com/ansible/galaxy.html#the-ansible-galaxy-command-line-tool) on the remote machine. By default, this is empty. +- `galaxycommand` (string) - The command to invoke ansible-galaxy. + By default, this is ansible-galaxy. + - `group_vars` (string) - a path to the directory containing ansible group variables on your local system to be copied to the remote machine. By default, this is empty. diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/ansible.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/ansible.html.md index 61719509..97e54869 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/ansible.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/ansible.html.md @@ -136,6 +136,16 @@ commonly useful Ansible variables: machine that the script is running on. This is useful if you want to run only certain parts of the playbook on systems built with certain builders. +## Debugging + +To debug underlying issues with Ansible, add `"-vvvv"` to `"extra_arguments"` to enable verbose logging. + +``` json +{ + "extra_arguments": [ "-vvvv" ] +} +``` + ## Limitations ### Redhat / CentOS @@ -231,3 +241,17 @@ This template should build a Windows Server 2012 image on Google Cloud Platform: ] } ``` + +### Too many SSH keys + +SSH servers only allow you to attempt to authenticate a certain number of times. All of your loaded keys will be tried before the dynamically generated key. If you have too many SSH keys loaded in your `ssh-agent`, the Ansible provisioner may fail authentication with a message similar to this: + +```console + googlecompute: fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Warning: Permanently added '[127.0.0.1]:62684' (RSA) to the list of known hosts.\r\nReceived disconnect from 127.0.0.1 port 62684:2: too many authentication failures\r\nAuthentication failed.\r\n", "unreachable": true} +``` + +To unload all keys from your `ssh-agent`, run: + +```console +$ ssh-add -D +``` diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/puppet-masterless.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/puppet-masterless.html.md index c630f841..b58d7825 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/puppet-masterless.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/puppet-masterless.html.md @@ -59,6 +59,10 @@ Optional parameters: variables](/docs/templates/engine.html) available. See below for more information. +- `guest_os_type` (string) - The target guest OS type, either "unix" or + "windows". Setting this to "windows" will cause the provisioner to use + Windows friendly paths and commands. By default, this is "unix". + - `extra_arguments` (array of strings) - This is an array of additional options to pass to the puppet command when executing puppet. This allows for customization of the `execute_command` without having to completely replace @@ -99,12 +103,13 @@ multiple manifests you should use `manifest_file` instead. executed to run Puppet are executed with `sudo`. If this is true, then the sudo will be omitted. -- `staging_directory` (string) - This is the directory where all the - configuration of Puppet by Packer will be placed. By default this - is "/tmp/packer-puppet-masterless". This directory doesn't need to exist but - must have proper permissions so that the SSH user that Packer uses is able - to create directories and write into this folder. If the permissions are not - correct, use a shell provisioner prior to this to configure it properly. +- `staging_directory` (string) - This is the directory where all the configuration + of Puppet by Packer will be placed. By default this is "/tmp/packer-puppet-masterless" + when guest OS type is unix and "C:/Windows/Temp/packer-puppet-masterless" when windows. + This directory doesn't need to exist but must have proper permissions so that the SSH + user that Packer uses is able to create directories and write into this folder. + If the permissions are not correct, use a shell provisioner prior to this to configure + it properly. - `working_directory` (string) - This is the directory from which the puppet command will be run. When using hiera with a relative path, this option @@ -117,17 +122,28 @@ multiple manifests you should use `manifest_file` instead. By default, Packer uses the following command (broken across multiple lines for readability) to execute Puppet: -``` liquid -cd {{.WorkingDir}} && \ -{{.FacterVars}}{{if .Sudo}} sudo -E {{end}} \ -{{if ne .PuppetBinDir \"\"}}{{.PuppetBinDir}}{{end}}puppet apply \ - --verbose \ - --modulepath='{{.ModulePath}}' \ - {{if ne .HieraConfigPath ""}}--hiera_config='{{.HieraConfigPath}}' {{end}} \ - {{if ne .ManifestDir ""}}--manifestdir='{{.ManifestDir}}' {{end}} \ - --detailed-exitcodes \ - {{if ne .ExtraArguments ""}}{{.ExtraArguments}} {{end}} \ - {{.ManifestFile}} +``` +cd {{.WorkingDir}} && +{{.FacterVars}} {{if .Sudo}} sudo -E {{end}} +puppet apply --verbose --modulepath='{{.ModulePath}}' +{{if ne .HieraConfigPath ""}}--hiera_config='{{.HieraConfigPath}}' {{end}} +{{if ne .ManifestDir ""}}--manifestdir='{{.ManifestDir}}' {{end}} +--detailed-exitcodes +{{if ne .ExtraArguments ""}}{{.ExtraArguments}} {{end}} +{{.ManifestFile}} +``` + +The following command is used if guest OS type is windows: + +``` +cd {{.WorkingDir}} && +{{.FacterVars}} && +puppet apply --verbose --modulepath='{{.ModulePath}}' +{{if ne .HieraConfigPath ""}}--hiera_config='{{.HieraConfigPath}}' {{end}} +{{if ne .ManifestDir ""}}--manifestdir='{{.ManifestDir}}' {{end}} +--detailed-exitcodes +{{if ne .ExtraArguments ""}}{{.ExtraArguments}} {{end}} +{{.ManifestFile}} ``` This command can be customized using the `execute_command` configuration. As you diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/puppet-server.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/puppet-server.html.md index 61a06d22..6adfd6b0 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/puppet-server.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/provisioners/puppet-server.html.md @@ -81,20 +81,38 @@ listed below: or `%PATH%` environment variable, but some builders (notably, the Docker one) do not run profile-setup scripts, therefore the path is usually empty. +- `guest_os_type` (string) - The target guest OS type, either "unix" or + "windows". Setting this to "windows" will cause the provisioner to use + Windows friendly paths and commands. By default, this is "unix". + - `execute_command` (string) - This is optional. The command used to execute Puppet. This has - various [configuration template - variables](/docs/templates/engine.html) available. See - below for more information. By default, Packer uses the following command: - -``` liquid -{{.FacterVars}} {{if .Sudo}} sudo -E {{end}} \ - {{if ne .PuppetBinDir \"\"}}{{.PuppetBinDir}}/{{end}}puppet agent --onetime --no-daemonize \ - {{if ne .PuppetServer \"\"}}--server='{{.PuppetServer}}' {{end}} \ - {{if ne .Options \"\"}}{{.Options}} {{end}} \ - {{if ne .PuppetNode \"\"}}--certname={{.PuppetNode}} {{end}} \ - {{if ne .ClientCertPath \"\"}}--certdir='{{.ClientCertPath}}' {{end}} \ - {{if ne .ClientPrivateKeyPath \"\"}}--privatekeydir='{{.ClientPrivateKeyPath}}' \ - {{end}} --detailed-exitcodes + various [configuration template variables](/docs/templates/engine.html) available. By default, + Packer uses the following command (broken across multiple lines for readability) to execute Puppet: + +``` +{{.FacterVars}} {{if .Sudo}}sudo -E {{end}} +{{if ne .PuppetBinDir ""}}{{.PuppetBinDir}}/{{end}}puppet agent +--onetime --no-daemonize +{{if ne .PuppetServer ""}}--server='{{.PuppetServer}}' {{end}} +{{if ne .Options ""}}{{.Options}} {{end}} +{{if ne .PuppetNode ""}}--certname={{.PuppetNode}} {{end}} +{{if ne .ClientCertPath ""}}--certdir='{{.ClientCertPath}}' {{end}} +{{if ne .ClientPrivateKeyPath ""}}--privatekeydir='{{.ClientPrivateKeyPath}}' {{end}} +--detailed-exitcodes +``` + +The following command is used if guest OS type is windows: + +``` +{{.FacterVars}} +{{if ne .PuppetBinDir ""}}{{.PuppetBinDir}}/{{end}}puppet agent +--onetime --no-daemonize +{{if ne .PuppetServer ""}}--server='{{.PuppetServer}}' {{end}} +{{if ne .Options ""}}{{.Options}} {{end}} +{{if ne .PuppetNode ""}}--certname={{.PuppetNode}} {{end}} +{{if ne .ClientCertPath ""}}--certdir='{{.ClientCertPath}}' {{end}} +{{if ne .ClientPrivateKeyPath ""}}--privatekeydir='{{.ClientPrivateKeyPath}}' {{end}} +--detailed-exitcodes ``` ## Default Facts diff --git a/vendor/github.com/mitchellh/packer/website/source/docs/templates/communicator.html.md b/vendor/github.com/mitchellh/packer/website/source/docs/templates/communicator.html.md index 423ebe8c..6109ca44 100644 --- a/vendor/github.com/mitchellh/packer/website/source/docs/templates/communicator.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/docs/templates/communicator.html.md @@ -75,8 +75,8 @@ The SSH communicator has the following options: - `ssh_bastion_username` (string) - The username to connect to the bastion host. -- `ssh_disable_agent` (boolean) - If true, SSH agent forwarding will be - disabled. Defaults to false. +- `ssh_disable_agent_forwarding` (boolean) - If true, SSH agent forwarding + will be disabled. Defaults to false. - `ssh_file_transfer_method` (`scp` or `sftp`) - How to transfer files, Secure copy (default) or SSH File Transfer Protocol. diff --git a/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/build-image.html.md b/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/build-image.html.md index 9da68041..2e9a6776 100644 --- a/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/build-image.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/build-image.html.md @@ -58,7 +58,7 @@ briefly. Create a file `example.json` and fill it with the following contents: "source_ami_filter": { "filters": { "virtualization-type": "hvm", - "name": "*ubuntu-xenial-16.04-amd64-server-*", + "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*", "root-device-type": "ebs" }, "owners": ["099720109477"], diff --git a/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/next.html.md b/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/next.html.md index 7ee31489..fcc35516 100644 --- a/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/next.html.md +++ b/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/next.html.md @@ -20,10 +20,6 @@ From this point forward, the most important reference for you will be the [documentation](/docs/index.html). The documentation is less of a guide and more of a reference of all the overall features and options of Packer. -If you're interested in learning more about how Packer fits into the HashiCorp -ecosystem of tools, read our [Atlas getting started -overview](https://atlas.hashicorp.com/help/intro/getting-started). - As you use Packer more, please voice your comments and concerns on the [mailing list or IRC](/community.html). Additionally, Packer is [open source](https://github.com/hashicorp/packer) so please contribute if you'd like diff --git a/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/remote-builds.html.md b/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/remote-builds.html.md deleted file mode 100644 index 593cd628..00000000 --- a/vendor/github.com/mitchellh/packer/website/source/intro/getting-started/remote-builds.html.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -layout: intro -sidebar_current: intro-getting-started-remote-builds -page_title: Remote Builds and Storage - Getting Started -description: |- - Up to this point in the guide, you have been running Packer on your local - machine to build and provision images on AWS and DigitalOcean. However, you - can use Atlas by HashiCorp to both run Packer builds remotely and store the - output of builds. ---- - -# Remote Builds and Storage - -Up to this point in the guide, you have been running Packer on your local -machine to build and provision images on AWS and DigitalOcean. However, you can -use [Atlas by HashiCorp](https://atlas.hashicorp.com) to run Packer builds -remotely and store the output of builds. - -## Why Build Remotely? - -By building remotely, you can move access credentials off of developer machines, -release local machines from long-running Packer processes, and automatically -start Packer builds from trigger sources such as `vagrant push`, a version -control system, or CI tool. - -## Run Packer Builds Remotely - -To run Packer remotely, there are two changes that must be made to the Packer -template. The first is the addition of the `push` -[configuration](https://www.packer.io/docs/templates/push.html), which sends the -Packer template to Atlas so it can run Packer remotely. The second modification -is updating the variables section to read variables from the Atlas environment -rather than the local environment. Remove the `post-processors` section for now -if it is still in your template. - -```json -{ - "variables": { - "aws_access_key": "{{env `aws_access_key`}}", - "aws_secret_key": "{{env `aws_secret_key`}}" - }, - "builders": [{ - "type": "amazon-ebs", - "access_key": "{{user `aws_access_key`}}", - "secret_key": "{{user `aws_secret_key`}}", - "region": "us-east-1", - "source_ami": "ami-9eaa1cf6", - "instance_type": "t2.micro", - "ssh_username": "ubuntu", - "ami_name": "packer-example {{timestamp}}" - }], - "provisioners": [{ - "type": "shell", - "inline": [ - "sleep 30", - "sudo apt-get update", - "sudo apt-get install -y redis-server" - ] - }], - "push": { - "name": "ATLAS_USERNAME/packer-tutorial" - } -} -``` - -To get an Atlas username, [create an account -here](https://atlas.hashicorp.com/account/new?utm_source=oss&utm_medium=getting-started&utm_campaign=packer). Once you have an account, you will need to contact -sales@hashicorp.com to start a trial, if you haven't already done so. - -Replace "ATLAS\_USERNAME" with your username in the above config. Generate an -Atlas token by navigating to https://atlas.hashicorp.com/settings/tokens and set -that token as an environment variable: `ATLAS_TOKEN=YOURTOKENHERE`. - -Then run `packer push example.json` to send the configuration to Atlas, which -automatically starts the build. - -This build will fail since neither `aws_access_key` or `aws_secret_key` are set -in the Atlas environment. To set environment variables in Atlas, navigate to -the [Builds tab](https://atlas.hashicorp.com/builds), click the -"packer-tutorial" build configuration that was just created, and then click -'variables' in the left navigation. Set `aws_access_key` and `aws_secret_key` -with their respective values. Now restart the Packer build by either clicking -'rebuild' in the Atlas UI or by running `packer push example.json` again. Now -when you click on the active build, you can view the logs in real-time. - --> **Note:** Whenever a change is made to the Packer template, you must -`packer push` to update the configuration in Atlas. - -## Store Packer Outputs - -Now we have Atlas building an AMI with Redis pre-configured. This is great, but -it's even better to store and version the AMI output so it can be easily -deployed by a tool like [Terraform](https://www.terraform.io). The `atlas` -[post-processor](/docs/post-processors/atlas.html) makes this process easier: - -```json -{ - "variables": ["..."], - "builders": ["..."], - "provisioners": ["..."], - "push": ["..."], - "post-processors": [{ - "type": "atlas", - "artifact": "ATLAS_USERNAME/packer-tutorial", - "artifact_type": "amazon.image" - }] -} -``` - -Update the `post-processors` block with your Atlas username, then -`packer push example.json` and watch the build kick off in Atlas! When the build -completes, the resulting artifact will be saved and stored in Atlas. diff --git a/vendor/github.com/mitchellh/packer/website/source/intro/hashicorp-ecosystem.html.md b/vendor/github.com/mitchellh/packer/website/source/intro/hashicorp-ecosystem.html.md deleted file mode 100644 index 1fb7bbaf..00000000 --- a/vendor/github.com/mitchellh/packer/website/source/intro/hashicorp-ecosystem.html.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -layout: intro -sidebar_current: intro-ecosystem -page_title: Packer and the HashiCorp Ecosystem - Introduction -description: |- - Learn how Packer fits in with the rest of the HashiCorp ecosystem of tools ---- - -# Packer and the HashiCorp Ecosystem - -HashiCorp is the creator of the open source projects Vagrant, Packer, Terraform, -Serf, Consul, Nomad, and the commercial product Atlas. Packer is just one piece -of the ecosystem HashiCorp has built to make application delivery a versioned, -auditable, repeatable, and collaborative process. To learn more about our -beliefs on the qualities of the modern datacenter and responsible application -delivery, read [The Atlas Mindset: Version Control for -Infrastructure](https://www.hashicorp.com/blog/atlas-mindset.html?utm_source=packer&utm_campaign=HashicorpEcosystem). - -If you are using Packer to build machine images and deployable artifacts, it's -likely that you need a solution for deploying those artifacts. Terraform is our -tool for creating, combining, and modifying infrastructure. - -Below are summaries of HashiCorp's open source projects and a graphic showing -how Atlas connects them to create a full application delivery workflow. - -# HashiCorp Ecosystem - -![Atlas Workflow](docs/atlas-workflow.png) - -[Atlas](https://atlas.hashicorp.com/?utm_source=packer&utm_campaign=HashicorpEcosystem) -is HashiCorp's only commercial product. It unites Packer, Terraform, and Consul -to make application delivery a versioned, auditable, repeatable, and -collaborative process. - -[Packer](https://www.packer.io/?utm_source=packer&utm_campaign=HashicorpEcosystem) -is a HashiCorp tool for creating machine images and deployable artifacts such as -AMIs, OpenStack images, Docker containers, etc. - -[Terraform](https://www.terraform.io/?utm_source=packer&utm_campaign=HashicorpEcosystem) -is a HashiCorp tool for creating, combining, and modifying infrastructure. In -the Atlas workflow Terraform reads from the artifact registry and provisions -infrastructure. - -[Consul](https://www.consul.io/?utm_source=packer&utm_campaign=HashicorpEcosystem) -is a HashiCorp tool for service discovery, service registry, and health checks. -In the Atlas workflow Consul is configured at the Packer build stage and -identifies the service(s) contained in each artifact. Since Consul is configured -at the build phase with Packer, when the artifact is deployed with Terraform, it -is fully configured with dependencies and service discovery pre-baked. This -greatly reduces the risk of an unhealthy node in production due to configuration -failure at runtime. - -[Serf](https://www.serf.io/?utm_source=packer&utm_campaign=HashicorpEcosystem) is -a HashiCorp tool for cluster membership and failure detection. Consul uses -Serf's gossip protocol as the foundation for service discovery. - -[Vagrant](https://www.vagrantup.com/?utm_source=packer&utm_campaign=HashicorpEcosystem) -is a HashiCorp tool for managing development environments that mirror -production. Vagrant environments reduce the friction of developing a project and -reduce the risk of unexpected behavior appearing after deployment. Vagrant boxes -can be built in parallel with production artifacts with Packer to maintain -parity between development and production. - -[Nomad](https://www.nomadproject.io/?utm_source=packer&utm_campaign=HashicorpEcosystem) -is a HashiCorp tool for managing a cluster of machines and running applications -on them. Nomad abstracts away machines and the location of applications, and -instead enables users to declare what they want to run and Nomad handles where -they should run and how to run them. diff --git a/vendor/github.com/mitchellh/packer/website/source/layouts/docs.erb b/vendor/github.com/mitchellh/packer/website/source/layouts/docs.erb index bb8b6fa7..133ebb3a 100644 --- a/vendor/github.com/mitchellh/packer/website/source/layouts/docs.erb +++ b/vendor/github.com/mitchellh/packer/website/source/layouts/docs.erb @@ -122,6 +122,9 @@ > OpenStack + > + Oracle OCI + > Parallels diff --git a/vendor/github.com/mitchellh/packer/website/source/layouts/intro.erb b/vendor/github.com/mitchellh/packer/website/source/layouts/intro.erb index 1963d3f0..ef4e0ca2 100644 --- a/vendor/github.com/mitchellh/packer/website/source/layouts/intro.erb +++ b/vendor/github.com/mitchellh/packer/website/source/layouts/intro.erb @@ -7,9 +7,6 @@ > Use Cases - > - Packer & HashiCorp - > Getting Started @@ -29,9 +26,6 @@ > Vagrant Boxes - > - Remote Builds - > Next Steps -- cgit v1.2.3