iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

clean up stale documentation for packer push

This commit is contained in:
Megan Marsh 2017-06-29 10:25:51 -07:00
parent 0b0fd408c4
commit b59383f88a
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
website/source/intro/getting-started/remote-builds.html.md
View File

@ -64,9 +64,14 @@ if it is still in your template.
```
To get an Atlas username, [create an account
here](https://atlas.hashicorp.com/account/new?utm_source=oss&utm_medium=getting-started&utm_campaign=packer).
Replace "ATLAS\_USERNAME" with your username, then run
`packer push -create example.json` to send the configuration to Atlas, which
here](https://atlas.hashicorp.com/account/new?utm_source=oss&utm_medium=getting-started&utm_campaign=packer). Once you have an account, you will need to contact
sales@hashicorp.com to start a trial, if you haven't already done so.
Replace "ATLAS\_USERNAME" with your username in the above config. Generate an
Atlas token by navigating to https://atlas.hashicorp.com/settings/tokens and set
that token as an environment variable: `ATLAS_TOKEN=YOURTOKENHERE`.
Then run `packer push example.json` to send the configuration to Atlas, which
automatically starts the build.
This build will fail since neither `aws_access_key` or `aws_secret_key` are set