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

Add prompt to use a specific directory for *.pkr.hcl (#8757) 

This improves usability as many users will still expect
to use `packer build config.pkr.hcl` having run
`packer build config.json` in the past.
This commit is contained in:
Mark Lewis 2020-02-18 09:55:30 +00:00 committed by GitHub
parent 5a87760702
commit 70752e0488
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/guides/hcl/variables/index.html.md.erb
View File

@ -19,7 +19,9 @@ Local variables can be a compound of input variables and local variables.
Let's create a file `variables.pkr.hcl` with the following contents. Let's create a file `variables.pkr.hcl` with the following contents.
-> **Note**: that the file can be named anything, since Packer loads all -> **Note**: that the file can be named anything, since Packer loads all
files ending in `.pkr.hcl` in a directory. files ending in `.pkr.hcl` in a directory. If you split your configuration
across multiple files, use `packer build <source directory>` to initiate
a build.
```hcl ```hcl
# variables.pkr.hcl # variables.pkr.hcl