Go to file
Wilken Rivera 1621ab59d8
tests/azure/arm: Update test image name (#10133)
I've run into a few cases where running the full test suite for the ARM
builder would fail because of conflicting image names. This is a
workaround for now the bigger fix is to have the acceptance clean up any
created images.

Results before change
```
the managed image named testBuilderAccManagedDiskWindows-1603151855 already exists in the resource group packer-acceptance-test, use the -force option to automatically delete it.
--- FAIL: TestBuilderAcc_ManagedDisk_Windows_Build_Resource_Group (0.66s)
```

Results after change
```
PASS
ok      github.com/hashicorp/packer/builder/azure/arm   2431.115s

```
2020-10-21 11:12:50 +02:00
.circleci Update build tools to latest supported versions 2020-09-30 11:22:13 -04:00
.github Update GitHub action (#9774) 2020-08-17 13:35:19 +02:00
builder tests/azure/arm: Update test image name (#10133) 2020-10-21 11:12:50 +02:00
cmd add sshkey package and ssh-keygen comand (#10101) 2020-10-19 10:24:34 +02:00
command add build.name to hcl code (#10114) 2020-10-16 10:57:42 +02:00
common Add HCL2 aws_secretsmanager function (#10124) 2020-10-20 16:21:40 +02:00
communicator adding basic support for OpenSSH CertificateFile support 2020-07-10 16:54:08 -07:00
contrib docs tweaks 2020-10-14 12:58:04 -07:00
examples [azure-chroot] Updating parameter `exlude_from_latest` to `exclude_from_latest` (#10034) 2020-10-07 11:08:33 +02:00
fix [azure-chroot] Updating parameter `exlude_from_latest` to `exclude_from_latest` (#10034) 2020-10-07 11:08:33 +02:00
hcl2template Add HCL2 aws_secretsmanager function (#10124) 2020-10-20 16:21:40 +02:00
helper add sshkey package and ssh-keygen comand (#10101) 2020-10-19 10:24:34 +02:00
packer Merge pull request #9996 from hashicorp/fix_9995 2020-10-05 13:00:51 -07:00
plugin/example Add golangci-lint to project (#8686) 2020-02-14 11:42:29 -05:00
post-processor Merge pull request #9968 from upodroid/google-impersonation 2020-10-06 11:32:03 -07:00
provisioner fix (provisioner/ansible): add checks for both roles and collections 2020-09-29 13:46:59 -04:00
scripts Fix: build.sh: give validateToolPresence a chance to inform the user (#9776) 2020-08-16 21:37:12 -04:00
template Add HCL2 aws_secretsmanager function (#10124) 2020-10-20 16:21:40 +02:00
test Fix line ending issues for test files (#10096) 2020-10-14 11:03:43 +02:00
vendor Merge pull request #10056 from marinsalinas/new_client 2020-10-16 15:28:54 -07:00
version Putting source back into Dev Mode 2020-09-30 18:45:29 +00:00
website Merge pull request #10116 from OblateSpheroid/GH8915 2020-10-20 14:41:09 -07: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 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-10-19 15:34:55 -07:00
CODEOWNERS update scaleway code owners (#9852) 2020-08-31 14:41:45 +02: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 make the default target generate dev builds. (#9811) 2020-08-25 10:11:38 +02:00
README.md Add CircleCI badge 2020-07-22 19:56:55 +02: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 JSON to HCL2 (minimal best-effort) transpiler (#9659) 2020-08-25 10:51:43 +02:00
config.go Replace kardianos/osext.Executable with os.Executable (#10048) 2020-10-06 10:59:32 +02:00
config_test.go Merge pull request #8616 from hashicorp/packer-plugin-path 2020-01-28 12:09:55 -08:00
go.mod Merge pull request #10056 from marinsalinas/new_client 2020-10-16 15:28:54 -07:00
go.sum Merge pull request #10056 from marinsalinas/new_client 2020-10-16 15:28:54 -07: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 no panicwrap in plugins 2020-10-01 13:32:00 -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 PkgGoDev 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.

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.