2 Commits (4e2d2961b6bc5df6b03ba1be8788c51e59ee783b)

Author	SHA1	Message	Date
Adrien Delorme	0f34592daa	packer init doc clarification (#10558) ... * Packer has no state like Terraform has * init command docs: tell where a plugin will be installed * docs: add a note that packer init does not work with legacy JSON templates * docs: add a not that packer init does not install single-plugin binaries * the plugin getter => packer init * Update init.mdx * grammar * link to how to install plugins manually * Update website/content/docs/commands/init.mdx Co-authored-by: Sylvia Moss <moss@hashicorp.com> * Update website/content/docs/commands/init.mdx Co-authored-by: Sylvia Moss <moss@hashicorp.com> Co-authored-by: Sylvia Moss <moss@hashicorp.com>	5 years ago
Adrien Delorme	ed091163be	HCL2 Parse packer.required_plugins block + packer init (#10304) ... This adds the new `required_plugins` block to be nested under the packer block. Example: ```hcl packer { required_plugins { aws = { version = ">= 2.7.0" source = "azr/aws" } azure = ">= 2.7.0" } } ``` For example on darwin_amd64 Packer will install those under : * "${PACKER_HOME_DIR}/plugin/github.com/azr/amazon/packer-plugin-amazon_2.7.0_x5.0_darwin_amd64" * "${PACKER_HOME_DIR}/plugin/github.com/hashicorp/azure/packer-plugin-azure_2.7.0_x5.0_darwin_amd64_x5" + docs + tests	5 years ago