packer-cn/builder/vmware/vmx
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.
2019-10-31 16:12:07 +01:00
..
builder.go Change back to make sure all durations are a time.Duration 2019-10-31 16:12:07 +01:00
builder_test.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
config.go commit old code generation tool 2019-10-15 12:56:42 +02:00
config.hcl2spec.go Force durations to be passed a strings 2019-10-31 11:47:19 +01:00
config_test.go tests actually test the floppies 2016-07-27 21:59:21 +01:00
step_clone_vmx.go rename interpolation context from ctx to ictx and contexts to ctx to avoid conflicts 2019-04-03 15:56:15 +02:00
step_clone_vmx_test.go Follow variable varName <-> statebag var_name convention 2018-04-27 20:09:19 +01:00
step_test.go move multistep imports to helper. 2018-01-24 17:09:15 -08:00