4 Commits (6adf1f6659fbb4522be557eec0ca4313eea74cd7)

Author	SHA1	Message	Date
Sylvia Moss	e44cb9d7e5	Add Amazon AMI data source to hcl_upgrade command (#10491)	5 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
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