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

Update website/content/docs/commands/init.mdx 

Co-authored-by: Sylvia Moss <moss@hashicorp.com>
This commit is contained in:
Adrien Delorme 2021-02-08 13:53:29 +01:00 committed by GitHub
parent b6cfe16444
commit a1b2e71005
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
website/content/docs/commands/init.mdx
View File

@ -18,11 +18,12 @@ have to [install the plugin manually](/docs/plugins#installing-plugins).
The `packer init` command is used to download Packer plugin binaries. This is
the first command that should be executed when working with a new or existing
template. This command is always safe to run multiple times. Though subsequent
runs may give errors, this command will never delete anything. Packer does not
currently have the notion of a state like Terraform has. In other words,
currently `packer init` is only in charge of installing packer
plugins.Currently, `packer init` can only fetch binaries from public projects on
*Github*. Github's public API, [limits the number of unauthenticated requests
runs may give errors, this command will never delete anything.
Packer does not currently have the notion of a state like Terraform has. In other words,
currently `packer init` is only in charge of installing packer plugins.
Currently, `packer init` can only fetch binaries from public projects on *Github*. Github's public API, [limits the number of unauthenticated requests
per hour one IP can
do](https://docs.github.com/en/developers/apps/rate-limits-for-github-apps#normal-user-to-server-rate-limits).
Packer will do its best to avoid hitting those limits and in an average local