Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
P
packer
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kristopher Ruzic
packer
Commits
8194846d
Commit
8194846d
authored
Feb 03, 2015
by
Seth Vargo
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update push command docs to remove `-token`
parent
75b4f50f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
16 deletions
+23
-16
website/source/docs/command-line/push.html.markdown
website/source/docs/command-line/push.html.markdown
+23
-16
No files found.
website/source/docs/command-line/push.html.markdown
View file @
8194846d
...
...
@@ -7,27 +7,34 @@ description: |-
# Command-Line: Push
The
`packer push`
Packer command takes a template and pushes it to a build
service. The build service will automatically build your Packer template and
expose the artifacts.
The
`packer push`
Packer command takes a template and pushes it to a Packer
build service such as
[
HashiCorp's Atlas
](
https://atlas.hashicorp.com
)
. The
build service will automatically build your Packer template and expose the
artifacts.
This command currently only sends templates to
[
Atlas
](
https://atlas.hashicorp.com
)
by HashiCorp, but the command will
be pluggable in the future with alternate implementations.
External build services such as Atlas make it easy to iterate on Packer
templates, especially when the builder you're running may not be easily
External build services such as HashiCorp's Atlas make it easy to iterate on
Packer templates, especially when the builder you are running may not be easily
accessable (such as developing
`qemu`
builders on Mac or Windows).
For the
`push`
command to work, the
[
push configuration
](
/docs/templates/push.html
)
For the
`push`
command to work, the
[
push configuration
](
/docs/templates/push.html
)
must be completed within the template.
## Options
*
`-create=true`
- If the build configuration matching the name of the push
doesn't exist, it will be created if this is true. This defaults to true.
*
`-token`
- An access token for authenticating the push to the Packer build
service such as Atlas. This can also be specified within the push
configuration in the template.
## Examples
Push a Packer template:
```
shell
$
packer push template.json
```
Push a Packer template with a custom token:
*
`-token=FOO`
- An access token for authenticating the push. This can also
be specified within the push configuration in the template. By setting this
in the template, you can take advantage of user variables.
```
shell
$
packer push
-token
ABCD1234 template.json
```
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment