9 Commits (1e86c49e321e16cd68d935b0d4bbbf05ba511b21)

Author	SHA1	Message	Date
Megan Marsh	efe11da4a3	Merge pull request #10254 from hashicorp/plugin-sdk-2 ... Plugin sdk 2	5 years ago
Megan Marsh	6402362018	create packer-plugin-sdk directory and begin moving the relevant folders into it.	6 years ago
Adrien Delorme	f44e912072	Update hcl2upgrade command to update env calls + tests (#10244)	6 years ago
Adrien Delorme	17ec88246f	hcl2_upgrade update (#10221) ... * handle template_dir, pwd funcs, handle min_packer_version * gotpl packer_version becomes hcl2 packer.version * uuid becomes hcl2 uuidv4 * test code with emojis * handle all cases were we cannot guess what the argument was * handle clean_resource_name cases * up docs	6 years ago
Peter Willis	a81811663a	Fix typos	6 years ago
Wilken Rivera	67cd123d1c	Merge pull request #9834 from hashicorp/azr-fix-hcl2_upgrade_random_generate ... hcl2_upgrade: fix a case where the generated type is wrong	6 years ago
Wilken Rivera	0e2a3e1058	command/hcl2_upgrade: Update description text for command ... Before change ``` Usage: packer [--version] [--help] <command> [<args>] Available commands are: build build image(s) from template console creates a console for testing variable interpolation fix fixes templates from old versions of packer hcl2_upgrade build image(s) from template inspect see components of a template validate check that a template is valid version Prints the Packer version ``` After change ``` Usage: packer [--version] [--help] <command> [<args>] Available commands are: build build image(s) from template console creates a console for testing variable interpolation fix fixes templates from old versions of packer hcl2_upgrade transform a JSON template into a HCL2 configuration inspect see components of a template validate check that a template is valid version Prints the Packer version ```	6 years ago
Adrien Delorme	0f00709fb6	hcl2_upgrade: fix a case where the generated type is wrong ... when it encounters map[string]interface{} or []interface{} types, hcl2_upgrade now takes the 'most complex' entry from those in order to tell wether this is going to be a body `body {}` or an attribute `attribute = {}`. Before that the hcl2_upgrade command could be a bit random there. A way better ( but may be somewhat hard ) way to do this would be to use the actual plugins structs in order to generate the HCL2.	6 years ago
Adrien Delorme	5ba134ac5b	JSON to HCL2 (minimal best-effort) transpiler (#9659) ... hcl2_upgrade transforms a JSON build-file in a HCL2 build-file. This starts a validated Packer core and from that core we generate an HCL 'block' per plugin/configuration. So for a builder, a provisioner, a post-processor or a variable. The contents of each block is just transformed as is and basically all fields are HCL2-ified. A generated field can be valid in JSON but invalid on HCL2; for example JSON templating (in mapstructure) allows to set arrays of strings - like `x = ["a", "b"]` - with single strings - like `x="a"` -, HCL does not allow this. Since JSON does not make the distinction between variables and locals, everything will be a variable. So variables that use other variables will not work. hcl2_upgrade tries to transform go templating interpolation calls to HCL2 calls when possible, leaving the go templating calls like they are in case it cannot. Work: * transpiler * tests * update hcl v2 library so that output looks great. * update docs	6 years ago