14 Commits (3571c585bb73e151e5bdaad007df161ce23cea7e)

Author	SHA1	Message	Date
Adrien Delorme	819329228a	Change back to make sure all durations are a time.Duration ... It is simply the best/simplest solution and trying to prevent users from passing and integer here would be like opening a can of worms. Because: * we cannot make mapstructure validate our duration string ( with an UnmarshalJSON func etc.) * we cannot make mapstructure spit a string instead of a duration and packer will decode-encode-decode config. * the hcl2 generated code asks for a string, so this will be enforced by default.	6 years ago
Adrien Delorme	bf3d9841c6	Force durations to be passed a strings ... Before this commit it was possible to set a duration using an integer or a float. Go's time.Duration is an int64 internally an mapstructure will take advantage of this and load the number as a int64 but `1` means one ns which is unexpected/confusing. To avoid confusion and enforce readability this forces users to pass a string with a unit for a duration; ex "56s".	6 years ago
Megan Marsh	da53ac99be	when using a slice of an imported field type, the Underlying still returned the slice rather than the element type.	6 years ago
Adrien Delorme	f6af5ecf07	Update mapstructure-to-hcl2.go ... make log/usage prompt prefix coherent	6 years ago
Adrien Delorme	9dac7908a5	Update mapstructure-to-hcl2.go ... better comments	6 years ago
Adrien Delorme	078ba7c8c3	commit old code generation tool ... for history	6 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.	6 years ago
Adrien Delorme	0fe48691e8	ignore doc fields containing `TODO`	7 years ago
Adrien Delorme	ec52f36af1	docs: escape pointer (*) parameters `*` => `\*` ... so that we don't get weird italics there and there	7 years ago
Adrien Delorme	349c3ef74b	cmd/struct-markdown: also generate docs from header comments of a struct ... & generate it for ISOConfig	7 years ago
Adrien Delorme	4ae10f08b2	docs: generate builders partials from struct comments	7 years ago
Adrien Delorme	f1917edd34	generate the comments for config struct of builders scraping doc website	7 years ago
Adrien Delorme	c7808aaf1f	do things locally	7 years ago
Adrien Delorme	31b66a63b1	scrape builder docs from https://www.packer.io/docs/ ... in order to get what is required and what is not.	7 years ago