Go to file
Wilken Rivera 3c282de6c3 Add maps for statically vendored components
This change adds a new set of maps for builders, provisioners, and
post-processors that store reference to components that were once part
of Packer and are now vendored. This file acts as a single place for
defining this vendored components, which are then merged into the main
components maps to be used in Packer.

Quick test to ensure the exoscale-import post-processor is still loaded
```
// Validate that exoscale-import is in the know post-procoessors list
~>  packer.test build docker_centos_shell_provisioner.pkr.hcl
Error: Unknown post-processor type "badlynamed-import"

  on docker_centos_shell_provisioner.pkr.hcl line 18:
  (source code not available)

known post-processors: [ucloud-import digitalocean-import docker-push
googlecompute-export manifest vsphere-template docker-tag vsphere checksum
docker-import exoscale-import yandex-export compress googlecompute-import
yandex-import vagrant-cloud alicloud-import amazon-import artifice shell-local
docker-save vagrant]

// Validate that exoscale-import get loaded
~>  packer.test build docker_centos_shell_provisioner.pkr.hcl
Error: Failed preparing post-processor-block "exoscale-import" ""

  on docker_centos_shell_provisioner.pkr.hcl line 18:
  (source code not available)

4 error(s) occurred:

* api_key must be set
* api_secret must be set
* image_bucket must be set
* template_zone must be set

==> Wait completed after 2 microseconds

==> Builds finished but no artifacts were created.
```
2021-03-09 10:09:13 -05:00
.circleci pin packer to golang 1.16 (#10702) 2021-03-02 11:43:58 +01:00
.github pin packer to golang 1.16 (#10702) 2021-03-02 11:43:58 +01:00
builder Merge pull request #10727 from tasha-marreiros/feature/gcp-windows-password-timeout-#10717 2021-03-09 09:40:51 -05:00
cmd Multi plugin naming (#10608) 2021-02-15 11:10:43 +01:00
command Add maps for statically vendored components 2021-03-09 10:09:13 -05:00
contrib docs tweaks 2020-10-14 12:58:04 -07:00
datasource Aws Secrets Manager data sources (#10505) 2021-01-22 14:49:45 +01:00
examples Extract plugin-specific examples to plugin directories (#10228) 2020-11-09 12:17:41 +01:00
fix fix fixer deprecated options conflict 2020-10-23 14:00:12 -07:00
hcl2template addrs: remove Plugin.ForDisplay func, the String one does the job 2021-02-15 15:32:42 +01:00
helper move provisioner acceptance tests into sdk alongside builder acceptance tests. Reorganize slightly to make sure no import cycles of doom get formed 2020-12-03 14:22:18 -08:00
packer remove this logline -- it is spammy and seems like a leftover dev debug line (#10665) 2021-02-22 11:20:44 +01:00
post-processor Remove "exoscale-import" post-processor 2021-03-09 10:01:05 -05:00
provisioner Merge pull request #10695 from hashicorp/docker_vendoring 2021-03-05 16:26:55 -08:00
scripts (2) Implement datasources (#10440) 2021-01-20 10:37:16 +01:00
test Fix line ending issues for test files (#10096) 2020-10-14 11:03:43 +02:00
vendor Vendor exoscale-import plugin 2021-03-09 10:02:30 -05:00
version Putting source back into Dev Mode 2021-02-17 16:12:20 +00:00
website Move to remote plugin docs for exoscale 2021-03-09 10:04:04 -05:00
.codecov.yml add step_add_floppy unit tests 2020-09-22 16:23:11 +02:00
.gitattributes Update .gitattributes 2020-10-02 11:06:02 +02:00
.gitignore Added support for IAM credential in the token field and YC_TOKEN env 2020-10-23 11:47:28 +03:00
.golangci.yml Add golangci-lint to project (#8686) 2020-02-14 11:42:29 -05:00
.hashibot.hcl update hashibot config not to comment when locking super old and stale issues 2020-04-03 11:37:34 -07:00
CHANGELOG.md update changelog 2021-02-19 10:43:31 -08:00
CODEOWNERS Remove "exoscale-import" post-processor 2021-03-09 10:01:05 -05:00
Dockerfile Use docker mirror 2020-10-29 11:05:41 -07:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile fix makefile 2020-12-11 13:37:03 -08:00
README.md readme: add white bg to packer logo in reamde.md (#10712) 2021-03-03 09:55:35 +01:00
Vagrantfile vagrantfile: add support for docker provider 2018-10-31 16:58:06 +03:00
background_check.go surface notimplemented errs too 2019-09-19 08:57:50 -07:00
background_check_openbsd.go copypasta 2019-09-18 10:54:35 -07:00
checkpoint.go remove sdk 2020-12-17 13:29:25 -08:00
commands.go HCL2 Parse packer.required_plugins block + packer init (#10304) 2021-02-02 18:05:04 +01:00
config.go HCL2 Parse packer.required_plugins block + packer init (#10304) 2021-02-02 18:05:04 +01:00
config_test.go HCL2 Parse packer.required_plugins block + packer init (#10304) 2021-02-02 18:05:04 +01:00
formatted.pkr.hcl HCL2 Parse packer.required_plugins block + packer init (#10304) 2021-02-02 18:05:04 +01:00
go.mod Vendor exoscale-import plugin 2021-03-09 10:02:30 -05:00
go.sum Vendor exoscale-import plugin 2021-03-09 10:02:30 -05:00
log.go log errors in scanner and manually close logging pipe if we hit an error in the scanner 2019-11-11 09:20:39 -08:00
main.go Add maps for statically vendored components 2021-03-09 10:09:13 -05:00
main_test.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
mlc_config.json Fix markdown link checker issues (#10575) 2021-02-05 16:46:53 -05:00
panic.go Add telemetry reporting through checkpoint 2017-06-15 13:21:11 -07:00
tty.go allow building packer on solaris by removing progress bar and tty imports 2019-05-07 15:58:49 +02:00
tty_solaris.go remove sdk 2020-12-17 13:29:25 -08:00

README.md

Packer

Build Status Discuss PkgGoDev GoReportCard codecov

HashiCorp Packer logo

Packer is a tool for building identical machine images for multiple platforms from a single source configuration.

Packer is lightweight, runs on every major operating system, and is highly performant, creating machine images for multiple platforms in parallel. Packer comes out of the box with support for many platforms, the full list of which can be found at https://www.packer.io/docs/builders.

Support for other platforms can be added via plugins.

The images that Packer creates can easily be turned into Vagrant boxes.

Quick Start

Note: There is a great introduction and getting started guide for those with a bit more patience. Otherwise, the quick start below will get you up and running quickly, at the sacrifice of not explaining some key points.

First, download a pre-built Packer binary for your operating system or compile Packer yourself.

After Packer is installed, create your first template, which tells Packer what platforms to build images for and how you want to build them. In our case, we'll create a simple AMI that has Redis pre-installed.

Save this file as quick-start.pkr.hcl. Export your AWS credentials as the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.

variable "access_key" {
  type    = string
  default = "${env("AWS_ACCESS_KEY_ID")}"
}

variable "secret_key" {
  type    = string
  default = "${env("AWS_SECRET_ACCESS_KEY")}"
}

locals { timestamp = regex_replace(timestamp(), "[- TZ:]", "") }

source "amazon-ebs" "quick-start" {
  access_key    = "${var.access_key}"
  ami_name      = "packer-example ${local.timestamp}"
  instance_type = "t2.micro"
  region        = "us-east-1"
  secret_key    = "${var.secret_key}"
  source_ami    = "ami-af22d9b9"
  ssh_username  = "ubuntu"
}

build {
  sources = ["source.amazon-ebs.quick-start"]
}

Next, tell Packer to build the image:

$ packer build quick-start.pkr.hcl
...

Packer will build an AMI according to the "quick-start" template. The AMI will be available in your AWS account. To delete the AMI, you must manually delete it using the AWS console. Packer builds your images, it does not manage their lifecycle. Where they go, how they're run, etc., is up to you.

Documentation

Comprehensive documentation is viewable on the Packer website at https://www.packer.io/docs.

Contributing to Packer

See CONTRIBUTING.md for best practices and instructions on setting up your development environment to work on Packer.

Unmaintained Plugins

As contributors' circumstances change, development on a community maintained plugin can slow. When this happens, the Packer team may mark a plugin as unmaintained, to clearly signal the plugin's status to users.

What does unmaintained mean?

  1. The code repository and all commit history will still be available.
  2. Documentation will remain on the Packer website.
  3. Issues and pull requests are monitored as a best effort.
  4. No active development will be performed by the Packer team.

If anyone form them community is interested in maintaining a community supported plugin, please feel free to submit contributions via a pull- request for review; reviews are generally prioritized over feature work when possible. For a list of open plugin issues and pending feature requests see the Packer Issue Tracker.