23 KiB

Raw Blame History

Contributing to Packer

First: if you're unsure or afraid of anything, just ask or submit the issue or pull request anyway. You won't be yelled at for giving your best effort. The worst that can happen is that you'll be politely asked to change something. We appreciate any sort of contributions, and don't want a wall of rules to get in the way of that.

However, for those individuals who want a bit more guidance on the best way to contribute to the project, read on. This document will cover what we're looking for. By addressing all the points we're looking for, it raises the chances we can quickly merge or address your contributions.

Issues

Reporting an Issue

Make sure you test against the latest released version. It is possible we already fixed the bug you're experiencing.
Run the command with debug output with the environment variable PACKER_LOG. For example: PACKER_LOG=1 packer build template.json. Take the entire output and create a gist for linking to in your issue. Packer should strip sensitive keys from the output, but take a look through just in case.
Provide a reproducible test case. If a contributor can't reproduce an issue, then it dramatically lowers the chances it'll get fixed. And in some cases, the issue will eventually be closed.
Respond promptly to any questions made by the Packer team to your issue. Stale issues will be closed.

Issue Lifecycle

The issue is reported.
The issue is verified and categorized by a Packer collaborator. Categorization is done via tags. For example, bugs are marked as "bugs" and simple fixes are marked as "good first issue".
Unless it is critical, the issue is left for a period of time (sometimes many weeks), giving outside contributors a chance to address the issue.
The issue is addressed in a pull request or commit. The issue will be referenced in the commit message so that the code that fixes it is clearly linked.
Sometimes, if you have a specialized environment or use case, the maintainers may ask for your help testing the patch. You are able to download an experimental binary of Packer containing the Pull Request's patch via from the Pull Request page on github. You can do this by scrolling to the "checks" section on github, and clicking "details" on the "store_artifacts" check. This will take you to Packer's Circle CI page for the build, and you will be able to click a tab named "Artifacts" which will contain zipped Packer binaries for each major OS architecture.
The issue is closed.

Setting up Go

If you have never worked with Go before, you will have to install its runtime in order to build packer.

This project always releases from the latest version of golang. Install go

Setting up Packer for dev

If/when you have go installed you can already go get packer and make in order to compile and test Packer. These instructions target POSIX-like environments (macOS, Linux, Cygwin, etc.) so you may need to adjust them for Windows or other shells. The instructions below are for go 1.7. or later.

Download the Packer source (and its dependencies) by running go get github.com/hashicorp/packer. This will download the Packer source to $GOPATH/src/github.com/hashicorp/packer.
When working on Packer, first cd $GOPATH/src/github.com/hashicorp/packer so you can run make and easily access other files. Run make help to get information about make targets.
Make your changes to the Packer source. You can run make in $GOPATH/src/github.com/hashicorp/packer to run tests and build the Packer binary. Any compilation errors will be shown when the binaries are rebuilding. If you don't have make you can simply run go build -o bin/packer . from the project root.
After running building Packer successfully, use $GOPATH/src/github.com/hashicorp/packer/bin/packer to build a machine and verify your changes work. For instance: $GOPATH/src/github.com/hashicorp/packer/bin/packer build template.json.
If everything works well and the tests pass, run go fmt on your code before submitting a pull-request.

Windows Systems

On windows systems you need at least the MinGW Tools, e.g. install via choco:

choco install mingw -y

This installs the GCC compiler, as well as a mingw32-make which can be used wherever this documentation mentions make

when building using go you also need to mention the windows executable extension

go build -o bin/packer.exe

Opening an Pull Request

Thank you for contributing! When you are ready to open a pull-request, you will need to fork Packer, push your changes to your fork, and then open a pull-request.

For example, my github username is cbednarski, so I would do the following:

git checkout -b f-my-feature
# Develop a patch.
git push https://github.com/cbednarski/Packer f-my-feature

From there, open your fork in your browser to open a new pull-request.

Note: Go infers package names from their file paths. This means go build will break if you git clone your fork instead of using go get on the main Packer project.

Note: See 'Working with forks' for a better way to use git push ....

Pull Request Lifecycle

You are welcome to submit your pull request for commentary or review before it is fully completed. Please prefix the title of your pull request with "[WIP]" to indicate this. It's also a good idea to include specific questions or items you'd like feedback on.
Once you believe your pull request is ready to be merged, you can remove any "[WIP]" prefix from the title and a core team member will review.
One of Packer's core team members will look over your contribution and either merge, or provide comments letting you know if there is anything left to do. We do our best to provide feedback in a timely manner, but it may take some time for us to respond. We may also have questions that we need answered about the code, either because something doesn't make sense to us or because we want to understand your thought process.
If we have requested changes, you can either make those changes or, if you disagree with the suggested changes, we can have a conversation about our reasoning and agree on a path forward. This may be a multi-step process. Our view is that pull requests are a chance to collaborate, and we welcome conversations about how to do things better. It is the contributor's responsibility to address any changes requested. While reviewers are happy to give guidance, it is unsustainable for us to perform the coding work necessary to get a PR into a mergeable state.
Once all outstanding comments and checklist items have been addressed, your contribution will be merged! Merged PRs will be included in the next Packer release. The core team takes care of updating the CHANGELOG.md as they merge.
In rare cases, we might decide that a PR should be closed without merging. We'll make sure to provide clear reasoning when this happens.

Tips for Working on Packer

Getting Your Pull Requests Merged Faster

It is much easier to review pull requests that are:

Well-documented: Try to explain in the pull request comments what your change does, why you have made the change, and provide instructions for how to produce the new behavior introduced in the pull request. If you can, provide screen captures or terminal output to show what the changes look like. This helps the reviewers understand and test the change.
Small: Try to only make one change per pull request. If you found two bugs and want to fix them both, that's awesome, but it's still best to submit the fixes as separate pull requests. This makes it much easier for reviewers to keep in their heads all of the implications of individual code changes, and that means the PR takes less effort and energy to merge. In general, the smaller the pull request, the sooner reviewers will be able to make time to review it.
Passing Tests: Based on how much time we have, we may not review pull requests which aren't passing our tests. (Look below for advice on how to run unit tests). If you need help figuring out why tests are failing, please feel free to ask, but while we're happy to give guidance it is generally your responsibility to make sure that tests are passing. If your pull request changes an interface or invalidates an assumption that causes a bunch of tests to fail, then you need to fix those tests before we can merge your PR.

If we request changes, try to make those changes in a timely manner. Otherwise, PRs can go stale and be a lot more work for all of us to merge in the future.

Even with everyone making their best effort to be responsive, it can be time-consuming to get a PR merged. It can be frustrating to deal with the back-and-forth as we make sure that we understand the changes fully. Please bear with us, and please know that we appreciate the time and energy you put into the project.

Working on forks

The easiest way to work on a fork is to set it as a remote of the Packer project. After following the steps in "Setting up Go to work on Packer":

Navigate to the code:

cd $GOPATH/src/github.com/hashicorp/packer
Add the remote by running:

git remote add <name of remote> <github url of fork>

For example:

git remote add mwhooker https://github.com/mwhooker/packer.git
Checkout a feature branch:

git checkout -b new-feature
Make changes.
(Optional) Push your changes to the fork:

git push -u <name of remote> new-feature

This way you can push to your fork to create a PR, but the code on disk still lives in the spot where the go cli tools are expecting to find it.

Go modules & go vendor

If you are submitting a change that requires new or updated dependencies, please include them in go.mod/go.sum and in the vendor/ folder. This helps everything get tested properly in CI.

Note that you will need to use go mod to do this. This step is recommended but not required.

Use go get <project> to add dependencies to the project and go mod vendor to make vendored copy of dependencies. See go mod quick start for examples.

Please only apply the minimal vendor changes to get your PR to work. Packer does not attempt to track the latest version for each dependency.

Code generation

Packer relies on go generate to generate a peg parser for boot commands, docs and HCL2's bridging code. Packer's testing suite will run make check-generate to check that all the generated files Packer needs are what they should be. make generate re-generates all these file and can take a while depending on your machine's performances. To make it faster it is recommended to run localized code generation. Say you are working on the Amazon builder: running go generate ./builder/amazon/... will do that for you. Make sure that the latest code generation tool is installed by running make install-gen-deps.

Code linting

Packer relies on golangci-lint for linting its Go code base, excluding any generated code created by go generate. Linting is executed on new files during Travis builds via make ci; the linting of existing code base is only executed when running make lint. Linting a large project like Packer is an iterative process so existing code base will have issues that are actively being fixed; pull-requests that fix existing linting issues are always welcomed 😄.

The main configuration for golangci-lint is the .golangci.yml in the project root. See golangci-lint --help for a list of flags that can be used to override the default configuration.

Run golangci-lint on the entire Packer code base.

make lint

Run golangci-lint on a single pkg or directory; PKG_NAME expands to /builder/amazon/...

make lint PKG_NAME=builder/amazon

Note: linting on Travis uses the --new-from-rev flag to only lint new files added within a branch or pull-request. To run this check locally you can use the ci-lint make target. See golangci-lint in CI for more information.

make ci-lint

Running Unit Tests

You can run tests for individual packages using commands like this:

make test TEST=./builder/amazon/...

Running Acceptance Tests

Packer has acceptance tests for various builders. These typically require an API key (AWS, GCE), or additional software to be installed on your computer (VirtualBox, VMware).

If you're working on a new builder or builder feature and want to verify it is functioning (and also hasn't broken anything else), we recommend running the acceptance tests.

Warning: The acceptance tests create/destroy/modify real resources, which may incur costs for real money. In the presence of a bug, it is possible that resources may be left behind, which can cost money even though you were not using them. We recommend running tests in an account used only for that purpose so it is easy to see if there are any dangling resources, and so production resources are not accidentally destroyed or overwritten during testing.

To run the acceptance tests, invoke make testacc:

make testacc TEST=./builder/amazon/ebs
...

The TEST variable lets you narrow the scope of the acceptance tests to a specific package / folder. The TESTARGS variable is recommended to filter down to a specific resource to test, since testing all of them at once can sometimes take a very long time.

To run only a specific test, use the -run argument:

make testacc TEST=./builder/amazon/ebs TESTARGS="-run TestBuilderAcc_forceDeleteSnapshot"

Acceptance tests typically require other environment variables to be set for things such as API tokens and keys. Each test should error and tell you which credentials are missing, so those are not documented here.

Running Provisioners Acceptance Tests

To run the Provisioners Acceptance Tests you should use both ACC_TEST_BUILDERS and ACC_TEST_PROVISIONERS variables to tell which provisioner and builder the test should be run against.

Examples of usage:

Run the Shell provisioner acceptance tests against the Amazon EBS builder.

ACC_TEST_BUILDERS=amazon-ebs ACC_TEST_PROVISIONERS=shell go test ./provisioner/shell/... -v -timeout=1h

Do the same but using the Makefile

ACC_TEST_BUILDERS=amazon-ebs ACC_TEST_PROVISIONERS=shell make provisioners-acctest

Run the all Shell and Powershell provisioners acceptance tests against the Amazon EBS builder.

ACC_TEST_BUILDERS=amazon-ebs ACC_TEST_PROVISIONERS=shell,powershell make provisioners-acctest

Run the all provisioners acceptance tests against the Amazon EBS builder.

ACC_TEST_BUILDERS=amazon-ebs ACC_TEST_PROVISIONERS=all make provisioners-acctest

Run the all provisioners acceptance tests against all builders whenever they are compatible.
```
ACC_TEST_BUILDERS=all ACC_TEST_PROVISIONERS=all make provisioners-acctest
```

Both ACC_TEST_BUILDERS and ACC_TEST_PROVISIONERS allows defining a list of builders and provisioners separated by comma (e.g. ACC_TEST_BUILDERS=amazon-ebs,virtualbox-iso)

Writing Provisioner Acceptance Tests

Packer has an already implemented structure that will run the provisioner against builders and you can find it in helper/tests/acc/provisioners.go. All provisioners should use this structure in their acceptance tests.

To start writing a new provisioner acceptance test, you should add a test file named as provisioner_acc_test.go in the provisioner folder and the package should be <provisioner>_test. This file should have a struct that will implement the ProvisionerAcceptance interface.

type ProvisionerAcceptance interface {
	GetName() string
	GetConfig() (string, error)
	GetProvisionerStore() packer.MapOfProvisioner
	IsCompatible(builder string, vmOS string) bool
	RunTest(c *command.BuildCommand, args []string) error
}

GetName() should return the provisioner type. For example for the Shell provisioner the method returns "shell".
GetConfig() should read a text file with the json configuration block for the provisioner and any other necessary provisioner. For the Shell one the file contains:
```
{
  "type": "shell",
  "inline": [
    "echo {{ build `ID`}} > provisioner.{{ build `PackerRunUUID`}}.txt"
  ]
},
{
    "type": "file",
    "source": "provisioner.{{ build `PackerRunUUID`}}.txt",
    "destination": "provisioner.shell.{{ build `PackerRunUUID`}}.txt",
    "direction": "download"
}
```
The file should be placed under the test-fixtures folder. In this case, it's necessary to use the File provisioner to validate if the Shell provisioner test is successful or not. This config should be returned as string that will be later merged with the builder config into a full template.

GetProvisionerStore() this returns the provisioner store where we declare the available provisioners for running the build. For the Shell provisioners this is:

  func (s *ShellProvisionerAccTest) GetProvisionerStore() packer.MapOfProvisioner {
  	return packer.MapOfProvisioner{
  		"shell": func() (packer.Provisioner, error) { return &shell.Provisioner{}, nil },
  		"file":  func() (packer.Provisioner, error) { return &file.Provisioner{}, nil },
  	}
  }

IsCompatible(builder string, vmOS string) returns true or false whether the provisioner should run against a specific builder or/and specific OS.

RunTest(c *command.BuildCommand, args []string) it will actually run the build and return any error if it fails the validations. For the Shell provisioner this is:

  func (s *ShellProvisionerAccTest) RunTest(c *command.BuildCommand, args []string) error {
  	// Provisioner specific setup
  	UUID := os.Getenv("PACKER_RUN_UUID")
  	if UUID == "" {
  		UUID, _ = uuid.GenerateUUID()
  		os.Setenv("PACKER_RUN_UUID", UUID)
  	}
  	file := "provisioner.shell." + UUID + ".txt"
  	defer testutils.CleanupFiles(file)

  	// Run build
	// All provisioner acc tests should contain this code and validation
  	if code := c.Run(args); code != 0 {
  		ui := c.Meta.Ui.(*packer.BasicUi)
  		out := ui.Writer.(*bytes.Buffer)
  		err := ui.ErrorWriter.(*bytes.Buffer)
  		return fmt.Errorf(
  			"Bad exit code.\n\nStdout:\n\n%s\n\nStderr:\n\n%s",
  			out.String(),
  			err.String())
  	}

  	// Any other extra specific validation
  	if !testutils.FileExists(file) {
  		return fmt.Errorf("Expected to find %s", file)
  	}
  	return nil
  }

After writing the struct and implementing the interface, now is time to write the test that will run all of this code you wrote. Your test should be like:

func TestShellProvisioner(t *testing.T) {
	acc.TestProvisionersPreCheck("shell", t)
	acc.TestProvisionersAgainstBuilders(new(ShellProvisionerAccTest), t)
}

If the environment variable ACC_TEST_PROVISIONERS is set as all or contains the provisioner type, then the test should run, otherwise the test should skip. In case of running it, you'll need to call the helper function acc.TestProvisionersAgainstBuilders passing a pointer to the test struct created above and the test testing pointer.

The method TestProvisionersAgainstBuilders will run the provisioner against all available and compatible builders. An available builder is the one that has the necessary code for running this type of test. In case the builder you want to run against is not available for testing, you can write it following the next steps.

To add a new builder to the available builders for provisioners acc testing, you'll need to create a new folder under the builder folder called acceptance and inside you create the builder_acceptance.go file and the package should be <builder>_acc. Like the provisioners, you'll need to create a struct that will implement the BuilderAcceptance interface.

type BuilderAcceptance interface {
	GetConfigs() (map[string]string, error)
	GetBuilderStore() packer.MapOfBuilder
	CleanUp() error
}

GetConfigs() should read a text file with the json configuration block for the builder and return a map of configs by OS type. For the Amazon EBS builder the file contains:
```
  {
    "type": "amazon-ebs",
    "ami_name": "packer-acc-test",
    "instance_type": "m1.small",
    "region": "us-east-1",
    "ssh_username": "ubuntu",
    "source_ami": "ami-0568456c",
    "force_deregister" : true,
    "tags": {
      "packer-test": "true"
    }
  }
```
The file should be placed under the test-fixtures folder. In case you need to make references to another file, you'll need to add the relative path to provisioners folder like: ../../builder/amazon/ebs/acceptance/test-fixtures/file.txt.

GetBuilderStore() this returns the builder store where we declare the available builders for running the build. For the Amazon EBS builder this is:

func (s *AmazonEBSAccTest) GetBuilderStore() packer.MapOfBuilder {
    return packer.MapOfBuilder{
        "amazon-ebs": func() (packer.Builder, error) { return &amazonebsbuilder.Builder{}, nil },
    }
}

CleanUp() cleans any resource created by the builder whether local or remote.

Once you created the builder necessary code, the last step is adding it to the BuildersAccTest map in helper/tests/acc/provisioners.go.

var BuildersAccTest = map[string]BuilderAcceptance{
	...
	"amazon-ebs":     new(amazonEBS.AmazonEBSAccTest),
	...
}

Once you finish the steps, you should be ready to run your new provisioner acceptance test.

Debugging Plugins

Each packer plugin runs in a separate process and communicates via RPC over a socket therefore using a debugger will not work (be complicated at least).

But most of the Packer code is really simple and easy to follow with PACKER_LOG turned on. If that doesn't work adding some extra debug print outs when you have homed in on the problem is usually enough.

23 KiB Raw Blame History