Go to file
RedTail72 374f82b978
buidler/vsphere-iso: ISOUrl Fix (#9321)
* ISOUrl Fix

Added the check for ISOUrls back in addition to a check for RawSingleISOUrl.  This should allow both ISOUrls[] or ISOUrl to work while not requiring them all the time.

* Update config.go

Fixed formatting.
2020-06-01 15:27:26 -04:00
.circleci Interpolate generatedData in the Inspec provisioner (#9262) 2020-05-20 15:43:41 -04:00
.github Merge pull request #9006 from hashicorp/provisioner_acc_contributing 2020-04-07 16:02:16 -07:00
builder buidler/vsphere-iso: ISOUrl Fix (#9321) 2020-06-01 15:27:26 -04:00
cmd appease linter 2020-05-29 09:40:31 -07:00
command Json vs HCL2 parity refactor (#9301) 2020-05-28 10:43:58 +02:00
common HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
communicator show a better error message in ssh.scpSession (#9217) 2020-05-13 15:57:05 +02:00
contrib Fix zsh auto-completion 2019-09-26 12:13:02 +01:00
examples builder/hyperone: Add examples for HCL syntax 2020-05-19 01:20:25 +02:00
fix add disk_size, disk_thin_provisioned, and disk_eagerly_scrub to the DeprecatedOptions field. 2020-05-29 09:45:36 -07:00
hcl2template HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
helper update deprecated options 2020-05-29 10:19:02 -07:00
packer move this to after the prepare() is successful so that we don't try to run builds that didn't prepare successfully. 2020-05-28 11:34:00 -07:00
plugin/example Add golangci-lint to project (#8686) 2020-02-14 11:42:29 -05:00
post-processor HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
provisioner HCL2: generate hcl tags with go-cty tags too (#9306) 2020-05-28 11:19:00 +02:00
scripts slow down the changelog script to prevent rate limiting (#9172) 2020-05-05 20:22:25 -04:00
template remove outdated comment 2020-05-29 09:43:31 -07:00
test builder/hyperone: Add tests for HCL syntax 2020-05-19 01:21:00 +02:00
vendor Drop the iso_checksum_type & iso_checksum_url fields (#8437) 2020-05-28 11:02:09 +02:00
version update to v1.6.0-dev 2020-05-01 15:45:34 -07:00
website Fix typo in Ansible Provisioner Docs 2020-06-01 09:53:54 -04:00
.codecov.yml remove codecov status (#9225) 2020-05-14 16:02:51 +02:00
.gitattributes clean up documentation for new NIC and storage params 2020-04-13 14:28:50 -04:00
.gitignore scrape builder docs from https://www.packer.io/docs/ 2019-06-05 16:41:20 +02: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 2020-05-29 15:51:54 -07:00
CODEOWNERS Add CODEOWNERS of bats tests (#9259) 2020-05-19 15:05:57 -04:00
Dockerfile dockerfile: add minimal image with provisioners support 2018-10-31 16:58:06 +03:00
LICENSE LICENSE: MPL2 2013-06-24 14:29:15 -07:00
Makefile add generator to create a list of all the deprecated options that the fixers fix 2020-05-29 09:40:31 -07:00
README.md Add Codecov badge and remove report style (#8896) 2020-03-16 15:59:55 +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 move packer to hashicorp 2017-04-04 13:39:01 -07:00
commands.go implement a packer console analogous to the terraform console 2019-06-05 16:35:22 -07:00
config.go make period stripping more strict so that users can disable provisiners by adding .old or whatever; this is pretty typical convention. 2020-02-13 12:59:47 -08:00
config_test.go Merge pull request #8616 from hashicorp/packer-plugin-path 2020-01-28 12:09:55 -08:00
go.mod Drop the iso_checksum_type & iso_checksum_url fields (#8437) 2020-05-28 11:02:09 +02:00
go.sum Drop the iso_checksum_type & iso_checksum_url fields (#8437) 2020-05-28 11:02:09 +02: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 enable force, debug, and on-error for hcl2 builds 2020-05-14 16:22:51 -07:00
main_test.go move packer to hashicorp 2017-04-04 13:39:01 -07: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 allow building packer on solaris by removing progress bar and tty imports 2019-05-07 15:58:49 +02:00

README.md

Packer

Build Status Windows Build Status GoDoc GoReportCard codecov

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/index.html.

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.json. Export your AWS credentials as the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.

{
  "variables": {
    "access_key": "{{env `AWS_ACCESS_KEY_ID`}}",
    "secret_key": "{{env `AWS_SECRET_ACCESS_KEY`}}"
  },
  "builders": [{
    "type": "amazon-ebs",
    "access_key": "{{user `access_key`}}",
    "secret_key": "{{user `secret_key`}}",
    "region": "us-east-1",
    "source_ami": "ami-af22d9b9",
    "instance_type": "t2.micro",
    "ssh_username": "ubuntu",
    "ami_name": "packer-example {{timestamp}}"
  }]
}

Next, tell Packer to build the image:

$ packer build quick-start.json
...

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:

https://www.packer.io/docs

Developing Packer

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