4 Commits (70aa0516deb7cd0d03d321fa025fa5ae581bb883)

Author	SHA1	Message	Date
Megan Marsh	da53ac99be	when using a slice of an imported field type, the Underlying still returned the slice rather than the element type.	7 years ago
Adrien Delorme	f6af5ecf07	Update mapstructure-to-hcl2.go ... make log/usage prompt prefix coherent	7 years ago
Adrien Delorme	9dac7908a5	Update mapstructure-to-hcl2.go ... better comments	7 years ago
Adrien Delorme	0eb9090dcf	Create mapstructure-to-hcl2.go ... mapstructure-to-hcl2 fills the gaps between hcl2 and mapstructure for Packer By generating a struct that the HCL2 ecosystem understands making use of mapstructure tags. Packer heavily uses the mapstructure decoding library to load/parse user config files. Packer now needs to move to HCL2. Here are a few differences/gaps betweens hcl2 and mapstructure: * in HCL2 all basic struct fields (string/int/struct) that are not pointers are required ( must be set ). In mapstructure everything is optional. * mapstructure allows to 'squash' fields (ex: Field CommonStructType `mapstructure:",squash"`) this allows to decorate structs and reuse configuration code. HCL2 parsing libs don't have anything similar. mapstructure-to-hcl2 will parse Packer's config files and generate the HCL2 compliant code that will allow to not change any of the current builders in order to move to HCL2 to softly move to HCL2.	7 years ago