97 Commits (ef9c2e65f6905db96c661fdc4e1921f5c11b51f7)

Author	SHA1	Message	Date
hashicorp-copywrite[bot]	6af0b29558	[COMPLIANCE] Update Copyright and License Headers	3 months ago
Sebastien Dionne	3cb0cd490e	Fix typos and linguistic errors in documentation ... Signed-off-by: Sebastien Dionne <survivant00@gmail.com>	4 months ago
Lucas Bajolet	e8d3a55b5f	packer: address errcheck lint errors ... In a couple places in the codebase we didn't check the errors from functions we execute. In some cases this is harmless (or at least ignorable), but others may need to log what went wrong, so for all the reported occurrences we either ignore explicitly or handle the error with a log.	2 years ago
Lucas Bajolet	8d4a9d66ab	config: rm mono-component support from config file (#12998) ... The global `PACKER_CONFIG` config file was already deprecated from Packer core, but now with 1.11.0 since we remove support for mono-component plugins, we are also removing the capability for that config file to declare them. Instead of silently not using those, Packer will now error with a message pointing to the web docs on how to manage their plugins with the updated workflows for Packer 1.11 and above.	2 years ago
Lucas Bajolet	a463abd73b	commands: introduce plugin as alias to plugins	2 years ago
Lucas Bajolet	7f056211d9	commands: rename plugin to execute ... The plugin and plugins command had a name that was close, and while plugin is not supposed to be directly called by Packer users, this could happen by accident while trying to execute packer plugins subcommands, and when it does, the error messages are far from explicit, so unless they understand what Packer is doing here, they'll likely be lost. To reduce the risk of confusion, we rename the command to run packer embedded components as execute.	2 years ago
Lucas Bajolet	e099c5c661	main: move Discover to DetectPluginBinaries ... When Packer is loaded, we used to perform plugin discovery. This was done for every call to Packer, including when it is executed as a plugin, arguably against what the comments document. Doing this as early in the loading process makes it harder to change this behaviour, as we'd need to introduce flags aside from the rest, and handle them manually, which is not optimal. Therefore, we change this: now when Packer starts executing, it will not attempt to discover installed plugins anymore, and instead will only try to load them when a configuration has been parsed, and is being used to perform actions (typically build/validate).	2 years ago
Lucas Bajolet	94aaff44a1	packer: only support one directory for plugins ... Since we're removing the alternative plugin installation directories in favour of only supporting installing them in the PACKER_PLUGIN_PATH directory, we only return one directory when getting the known plugin directories.	2 years ago
guoguangwu	7eb6a45cd4	chore: remove refs to deprecated io/ioutil ... Signed-off-by: guoguangwu <guoguangwu@magic-shield.com>	2 years ago
Wilken Rivera	48e8c3e680	Update version output for `-v` and `--version` flags ... The flags -v and --version are handled by the CLI runner, which outputs the raw version string. This change shortcuts the handling of the flags to force Packer to run the version subcommand. Closes: #12565	3 years ago
Lucas Bajolet	eb9e1a4795	packer: remove implicit required plugins ... Since this feature is no longer something we plan to activate later, as it contradicts with our efforts to remove bundled plugins, and encouraging users to move to either manually installing plugins, or managing them through `packer init', we clean-up the code for this feature.	3 years ago
hashicorp-copywrite[bot]	19055df3ec	[COMPLIANCE] License changes (#12568) ... * Updating the license from MPL to Business Source License Going forward, this project will be licensed under the Business Source License v1.1. Please see our blog post for more details at https://hashi.co/bsl-blog, FAQ at https://hashi.co/license-faq, and details of the license at www.hashicorp.com/bsl. * Update copyright file headers to BUSL-1.1 --------- Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>	3 years ago
hashicorp-copywrite[bot]	b7df3ca36f	[COMPLIANCE] Add Copyright and License Headers (#12254) ... Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>	3 years ago
Wilken Rivera	58fa1f96e2	Temporarily revert the use of indirect redirects for external plugins (#11430) ... The auto installation of external plugins via packer init only work for HCL templates. Since we have not officially removed all plugins (slated for 1.8.0) I am reverting this test change. Once 1.7.9 is released we can begin removing plugins and optimizing the redirect experience for JSON-only users.	4 years ago
Adrien Delorme	faeef90910	remove ansible plugin from bundled plugins	4 years ago
Adrien Delorme	8acd453065	remove vagrant plugin from bundled plugins	4 years ago
Adrien Delorme	bfe200d920	remove qemu plugin from bundled plugins	4 years ago
Adrien Delorme	d9d96169d8	remove googlecompute plugin from bundled plugins	4 years ago
Adrien Delorme	4efa69cfff	remove docker plugin from bundled plugins	4 years ago
Adrien Delorme	7a21f141c8	remove vsphere plugin from bundled plugins	4 years ago
Adrien Delorme	eea27b02d5	remove parallels plugin from bundled plugins	4 years ago
Adrien Delorme	36c30706f1	remove vmware plugin from bundled plugins	4 years ago
Adrien Delorme	eca7b442c1	remove virtualbox plugin from bundled plugins	4 years ago
Adrien Delorme	37ac5b260f	remove azure plugin from bundled plugins	4 years ago
Adrien Delorme	bb33cf9845	remove amazon plugin from bundled plugins	4 years ago
Adrien Delorme	c391c7f10b	make the exoscale plugin an implicit import	4 years ago
Megan Marsh	e8780bf7b8	add massive warning about error logging to WrappedMain	5 years ago
Wilken Rivera	c3e78d2c32	Update error messaging to bypass panicwrap only on non-recoverable ... errors While working on this change it was found that prefixing an error message with the ErrorPrefix string would trigger a copyOutput function that would copy any outputted string to Stderr, until a new ErrorPrefix or Outprefix string is encountered in the output. During background runs of Packer an error message with the ErrorPrefix was being outputted which was causing all output, including Stdout, to be written to Stderr. This change updates the logic to only override the Stdout logging for non-recoverable errors. The idea being that any non-recoverable error should bypass panicwrap so that user know an error occurred. All other errors should follow the same behavior that we had prior to Packer v1.7.1. Closes #10855	5 years ago
Megan Marsh	1b8e71ca1f	switch to using ui once it is initialized	5 years ago
Adrien Delorme	0e3fcb589b	Implicit required_plugin blocks (#10732) ... * used components that don't have a required_plugin block will make Packer 'implicitly' require those. These components are manually selected and commented for now. * add tests * docs	5 years ago
Megan Marsh	64a3219f69	fix error messaging in wrappedmain. Stderr gets eaten by panicwrap, so we need to write to stdout, which then gets unpacked into error and output messages using the ErrorPrefix and OutputPrefix (#10766)	5 years ago
Megan Marsh	c4a22e9a56	fix packer interpolation of packer log path (#10660)	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
Sylvia Moss	291121dd55	(2) Implement datasources (#10440)	5 years ago
Megan Marsh	88b7b0e14a	remove sdk	5 years ago
Megan Marsh	f179f01314	Modify struct-markdown generator code to work from different projct roots ... Modify makefile to call generate code properly, setting project root. 'make generate' now avoids deleting website code generated in the packer plugin sdk. For now it will be maintainers' responsibility to regenerate this docs code from the packer plugin sdk every release, and commit it to these folders manually. remove boot command generator code	5 years ago
Megan Marsh	39ab646236	move plugin and rpc code into sdk; other minor tweaks (#10359)	5 years ago
Megan Marsh	352f064b55	fix docker acceptance tests. Turns out they were broken on the main branch too; needed to move noop progress bar into the sdk to be used in the builder testui.	5 years ago
Megan Marsh	3681e2a7ee	fix pathing	5 years ago
sylviamoss	2c10c21445	move plugin discover tests to plugin pkg	5 years ago
Megan Marsh	d5971ca25e	fix tests by moving mock hooks and communicators, and BasicUi definition, into SDK	5 years ago
Megan Marsh	a6fdeca099	move logsecretfilter into packer sdk	5 years ago
Megan Marsh	001886670d	move Ui definition into the packer plugin sdk.	5 years ago
Megan Marsh	7d658149ea	update tests and website and generated partials to reflect new package format	5 years ago
Megan Marsh	1ffc358ada	move tmp helper func into packer-plugin-sdk	5 years ago
Dmitry Borodaenko	d18b7839b9	no panicwrap in plugins ... As of mitchellh/panicwrap#25, a call to panicwrap.Wrapped() unsets the cookie in the env, that makes packer plugin child process inherit an env without the panicwrap cookie and panicwrap itself. This trips up CleanupClients() in Packer's plugin client: instead of the real plugin server it now kills its panicwrap parent -- which doesn't forward SIGKILL to its child because it's not a signal that can be caught -- and ends up indefinitely waiting in client.Kill() for an EOF that will never come. This workaround is to not even try to panicwrap in a plugin server.	5 years ago
Megan Marsh	15ee44e857	review comments	5 years ago
Megan Marsh	ae8d359bf1	Switch to explicitly declaring TrackProgress on UI, using an underlying progress bar specifically stored on the struct. Export UiProgressTracker. These changes allow us to optionaly switch to the NoopProgressTracker when no TTY is set.	5 years ago
Megan Marsh	ee5635722b	enable force, debug, and on-error for hcl2 builds	6 years ago
nywilken	fb76323c4d	config: Fix loading external plugins from a packerconfig ... This change introduces a loadExternalComponent which can be used for loading a single plugin path. The function is a combination of the discoverSingle and discoverExternalComponents functions.	6 years ago