github.com/aspring/packer@v0.8.1-0.20150629211158-9db281ac0f89/website/source/docs/command-line/push.html.markdown (about) 1 --- 2 layout: "docs" 3 page_title: "Push - Command-Line" 4 description: |- 5 The `packer push` Packer command takes a template and pushes it to a build service that will automatically build this Packer template. 6 --- 7 8 # Command-Line: Push 9 10 The `packer push` Packer command takes a template and pushes it to a Packer 11 build service such as [HashiCorp's Atlas](https://atlas.hashicorp.com). The 12 build service will automatically build your Packer template and expose the 13 artifacts. 14 15 External build services such as HashiCorp's Atlas make it easy to iterate on 16 Packer templates, especially when the builder you are running may not be easily 17 accessable (such as developing `qemu` builders on Mac or Windows). 18 19 !> The Packer build service will receive the raw copy of your Packer template 20 when you push. **If you have sensitive data in your Packer template, you should 21 move that data into Packer variables or environment variables!** 22 23 For the `push` command to work, the [push configuration](/docs/templates/push.html) 24 must be completed within the template. 25 26 ## Options 27 28 * `-message` - A message to identify the purpose or changes in this Packer 29 template much like a VCS commit message. This message will be passed to the 30 Packer build service. This option is also available as a short option `-m`. 31 32 * `-token` - An access token for authenticating the push to the Packer build 33 service such as Atlas. This can also be specified within the push 34 configuration in the template. 35 36 * `-name` - The name of the build in the service. This typically 37 looks like `hashicorp/precise64`. 38 39 ## Examples 40 41 Push a Packer template: 42 43 ```shell 44 $ packer push -m "Updating the apache version" template.json 45 ``` 46 47 Push a Packer template with a custom token: 48 49 ```shell 50 $ packer push -token ABCD1234 template.json 51 ```