10 Commits (56aebbeda96df6fd30773d55544729145b9c35ea)

Author	SHA1	Message	Date
Adrien Delorme	78ac1e256b	better type for []NameValue in docs	6 years ago
Adrien Delorme	0a46bb9525	more precise docs	6 years ago
Adrien Delorme	b5e8750f5f	Change key/value to name/value to remain consistent with Terraform	6 years ago
Adrien Delorme	87d6b2433f	make generate	6 years ago
Adrien Delorme	6e6490d688	WIP	6 years ago
Megan Marsh	dde74232f2	Clearly document all template-engine-enabled options (#8770)	6 years ago
Adam Dobrawy	3b091e6046	builder/hyperone: fix & add tests for tags	6 years ago
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.	7 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".	7 years ago
Adrien Delorme	4ae10f08b2	docs: generate builders partials from struct comments	7 years ago