208afbebfa
The former way mock plugin sets were created meant that no API version was set, and since it's private in the SDK, it cannot be set outside of the package itself. Fortunately, there is a NewSet function we can call, which initialises a set properly so we can fill-in the information later. However, because all the set maps were created in a `var` section, we cannot create the set with `NewSet`, and then fill the information in (outside of if there was a fluent interface, but this isn't the case here). We therefore opted to keep the variables defined and accessible globally, but gone through a `init` function to initialise their values for tests. |
||
|---|---|---|
| .github | ||
| .release | ||
| acctest | ||
| builder | ||
| cmd | ||
| command | ||
| contrib/zsh-completion | ||
| datasource | ||
| examples | ||
| fix | ||
| hcl2template | ||
| helper | ||
| internal/hcp | ||
| packer | ||
| post-processor | ||
| provisioner | ||
| scripts | ||
| version | ||
| website | ||
| .copywrite.hcl | ||
| .gitattributes | ||
| .gitignore | ||
| .go-version | ||
| .golangci.yml | ||
| background_check.go | ||
| background_check_openbsd.go | ||
| CHANGELOG.md | ||
| checkpoint.go | ||
| CODEOWNERS | ||
| commands.go | ||
| config.go | ||
| config_test.go | ||
| Dockerfile | ||
| go | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| log.go | ||
| main.go | ||
| main_test.go | ||
| Makefile | ||
| panic.go | ||
| README.md | ||
| tty.go | ||
| tty_solaris.go | ||
| Vagrantfile | ||
Packer
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 supports various platforms through external plugin integrations, the full list of which can be found at https://developer.hashicorp.com/packer/integrations.
The images that Packer creates can easily be turned into Vagrant boxes.
Quick Start
Packer
There is a great introduction and getting started guide for building a Docker image on your local machine without using any paid cloud resources.
Alternatively, you can refer to getting started with AWS to learn how to build a machine image for an external cloud provider.
HCP Packer
HCP Packer registry stores Packer image metadata, enabling you to track your image lifecycle.
To get started with building an AWS machine image to HCP Packer for referencing in Terraform refer to the collection of HCP Packer Tutorials.
Documentation
Comprehensive documentation is viewable on the Packer website at https://developer.hashicorp.com/packer/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, HashiCorp may use GitHub's option to archive the plugin’s repository, to clearly signal the plugin's status to users.
What does unmaintained mean?
- The code repository and all commit history will still be available.
- Documentation will remain on the Packer website.
- Issues and pull requests are monitored as a best effort.
- No active development will be performed by HashiCorp.
If you are interested in maintaining an unmaintained or archived plugin, please reach out to us at packer@hashicorp.com.