packer

Commit Graph

Author	SHA1	Message	Date
Lucas Bajolet	9f6f0ba6a2	packer: pick protobuf/gob for serialisation (#13025 ) As we're trying to move away from gob for serialising data over the wire, this commit adds the capability for Packer to pick dynamically between gob or protobuf for the serialisation format to communicate with plugins. As it stands, if all the plugins discovered are compatible with protobuf, and we have not forced gob usage, protobuf will be the serialisation format picked. If any plugin is not compatible with protobuf, gob will be used for communicating with all the plugins that will be used over the course of a command.	1 year 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	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
Wilken Rivera	e8d5436228	Remove functions for detecting plugin usage With the removal of vendored_plugins we are no longer interested in tacking bundled plugins usage. For plugins such as file, null, or anything bultin into Packer we don't track because there is no way to install them outside of Packer, for now.	2 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
Lucas Bajolet	a2930bda4f	packer: warn on bundled plugins usage Since bundled plugins will be removed in an upcoming version of Packer, this commit adds a new warning message whenever a template uses one such plugin. This warning has been implemented on build, validate, console and the inspect subcommands. In addition to warning about the upcoming change and potential issue this will cause, this warning message proposes solutions to the user so they know what they'll have to do in order not to rely on those bundled plugins later.	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
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
Adrien Delorme	52d2d7fe5f	Copy `MapOf...` plugin types back into Packer core (#10466 ) * move maps of plugins back in core * go mod vendor * more fixes * fix imports * Update core_test.go * fix build * more fixes * more fixes * up vendors after fixing sdk * Update post_processor_mock.hcl2spec.go * Leave implementatino of MapOf in the sdk for plugi tests Other wise use the interface * go mod tidy * add MapOfDatasource type too	5 years ago
Megan Marsh	88b7b0e14a	remove sdk	5 years ago
Adrien Delorme	72c1912b60	allow to discover & start packer-plugin-* muliplugin binaries (#10277 ) This add : * discovery of `packer-plugin-` binaries from the known folders and ask them to describe themselves tests For testing: in go we create a bash script that in turn calls back to Go. I could not make the tests to work on windows and then would like to postpone testing this for when we know more about the finite layout of this feature. That is mainly: how things are going to work with init, versioning and such.	5 years ago
Megan Marsh	5576bb5caa	move packer config constants next to the packer config	5 years ago
sylviamoss	2c10c21445	move plugin discover tests to plugin pkg	5 years ago
Megan Marsh	b69d69095e	move postprocessor to sdk, fix generation code	5 years ago
Megan Marsh	ada91b24e9	extract builder interface to sdk	5 years ago
Megan Marsh	56a45b04ab	Move hook and communicator definitions to packer-plugin-sdk	5 years ago
zhsj	ef9713b348	Replace kardianos/osext.Executable with os.Executable (#10048 ) os.Executable is available since go1.8 https://github.com/kardianos/osext/blob/master/osext_go18.go	5 years ago
Megan Marsh	ced2e945e3	make period stripping more strict so that users can disable provisiners by adding .old or whatever; this is pretty typical convention.	6 years ago
Megan Marsh	817957fe4f	Merge pull request #8616 from hashicorp/packer-plugin-path add PACKER_PLUGIN_PATH for plugin discovery	6 years ago
Megan Marsh	a163ff7388	swap ordering so PACKER_PLUGIN_PATH gets precedence	6 years ago
nywilken	c93a076698	config: Update loading of packerconfig to only log when a plugin is loaded Before this change loading of a packerconfig would display `loaded plugin ...` for any plugin defined in the packerconfig - even if it didn't exist on disk. This change updates how plugins defined in packerconfig are loaded to ensure that only successfully loaded plugins get the lovely message `loaded plugin ...`. For any plugin that fails to load Packer will log that it failed to load the plugin and continue processing any other defined plugins. * Add a test to ensure loadSingleComponent errors when plugin does not exists	6 years ago
Megan Marsh	83ecebbf37	add PACKER_PLUGIN_PATH for plugin discovery	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
Megan Marsh	d95b0122f8	Merge pull request #8542 from TJM/plugin_logs Parse out -PACKERSPACE- before looking for exec	6 years ago
Tommy McNeely	469a4d2a11	Fix names of range variables to reduce confusion and remove overriden plugin name	6 years ago
Tommy McNeely	72112ccae2	Make the path assignment less confusing	6 years ago
Tommy McNeely	3177a5413c	Fix external plugins path was blank	6 years ago
Tommy McNeely	9d85aa36ec	Parse out -PACKERSPACE- before looking for exec	6 years ago
Adrien Delorme	0785c2f6fc	build using HCL2 (#8423 ) This follows #8232 which added the code to generate the code required to parse HCL files for each packer component. All old config files of packer will keep on working the same. Packer takes one argument. When a directory is passed, all files in the folder with a name ending with “.pkr.hcl” or “.pkr.json” will be parsed using the HCL2 format. When a file ending with “.pkr.hcl” or “.pkr.json” is passed it will be parsed using the HCL2 format. For every other case; the old packer style will be used. ## 1. the hcl2template pkg can create a packer.Build from a set of HCL (v2) files I had to make the packer.coreBuild (which is our one and only packer.Build ) a public struct with public fields ## 2. Components interfaces get a new ConfigSpec Method to read a file from an HCL file. This is a breaking change for packer plugins. a packer component can be a: builder/provisioner/post-processor each component interface now gets a `ConfigSpec() hcldec.ObjectSpec` which allows packer to tell what is the layout of the hcl2 config meant to configure that specific component. This ObjectSpec is sent through the wire (RPC) and a cty.Value is now sent through the already existing configuration entrypoints: Provisioner.Prepare(raws ...interface{}) error Builder.Prepare(raws ...interface{}) ([]string, error) PostProcessor.Configure(raws ...interface{}) error close #1768 Example hcl files: ```hcl // file amazon-ebs-kms-key/run.pkr.hcl build { sources = [ "source.amazon-ebs.first", ] provisioner "shell" { inline = [ "sleep 5" ] } post-processor "shell-local" { inline = [ "sleep 5" ] } } // amazon-ebs-kms-key/source.pkr.hcl source "amazon-ebs" "first" { ami_name = "hcl2-test" region = "us-east-1" instance_type = "t2.micro" kms_key_id = "c729958f-c6ba-44cd-ab39-35ab68ce0a6c" encrypt_boot = true source_ami_filter { filters { virtualization-type = "hvm" name = "amzn-ami-hvm-????.??.?.????????-x86_64-gp2" root-device-type = "ebs" } most_recent = true owners = ["amazon"] } launch_block_device_mappings { device_name = "/dev/xvda" volume_size = 20 volume_type = "gp2" delete_on_termination = "true" } launch_block_device_mappings { device_name = "/dev/xvdf" volume_size = 500 volume_type = "gp2" delete_on_termination = true encrypted = true } ami_regions = ["eu-central-1"] run_tags { Name = "packer-solr-something" stack-name = "DevOps Tools" } communicator = "ssh" ssh_pty = true ssh_username = "ec2-user" associate_public_ip_address = true } ```	6 years ago
Megan Marsh	5d5189a9a2	only log when external plugin is used, since this is the much rarer event	6 years ago
Adrien Delorme	5a6dffde9a	use port as ints	7 years ago
Matthew Hooker	81522dced0	move packer to hashicorp	9 years ago
Matthew Hooker	79287d7e47	simplify some code	9 years ago
Chris Bednarski	010fa977cf	Change to explicit comparison with MagicCookieValue	9 years ago
Chris Bednarski	3935703286	Supress plugin discovery from plugins, which is redundant and noisy in the logs	9 years ago
Mark Peek	1c7a855302	Switch osext package from mitchellh -> kardianos #2842	10 years ago
Mark Peek	ba7814b0ed	Merge pull request #2846 from markpeek/packer-tmp Create docker temp files under packer.d when TMPDIR is not set	10 years ago
Chris Bednarski	e080e73b04	Add some exit codes and use a constant for -PACKERSPACE-	10 years ago
Chris Bednarski	d09a9ab0c7	Implemented internal plugins - Internal plugins are compiled into the same packer binary and invoked through the plugin command - Search paths allow disk-based plugins to override and should function as normal - This should allow for a 94% space savings vs statically compiling all the plugins as separate binaries.. approximately 24mb vs 431mb	10 years ago
Mark Peek	38c81cf3e3	Move ConfigFile() and ConfigDir() from package main to packer	11 years ago
Mitchell Hashimoto	e88fa43cfe	find proper extension	11 years ago
Mitchell Hashimoto	9514be0df0	lowercase the extension of plugins just in case	11 years ago
Mitchell Hashimoto	03032c26fb	ignore non-exe plugins on Windows [GH-2173]	11 years ago
Mitchell Hashimoto	1ee2b014a6	packer: remove Ui/Cache from CoreConfig	11 years ago
Mitchell Hashimoto	dc74ec5612	packer: remove Environment	11 years ago
Mitchell Hashimoto	9d89ca8e07	command: build should be converted to new API, compiles	11 years ago
Aneesh Agrawal	63597af8bb	Clarify the plugin discovery search & priority orders.	11 years ago
Matt Hollingsworth	816f722e3b	Fix typo in log statement	11 years ago
Mitchell Hashimoto	c51cd3e39c	remove command configs	11 years ago

1 2 3

114 Commits (karthik/powershell_encoding)