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
..
artifact.go	[lxc] go fmt our files	2017-09-05 15:18:07 -07:00
builder.go	change Builder to be passed a context for cancellation	2019-04-03 15:55:55 +02:00
builder_test.go	cleanup imports and rebase artifacts	2017-09-05 15:23:22 -07:00
command.go	don't chown to close the security issue	2018-05-16 21:40:22 +00:00
communicator.go	allow a provisioner to timeout	2019-04-08 20:09:21 +02:00
communicator_test.go	run goimports	2018-01-22 17:21:10 -08:00
config.go	Change back to make sure all durations are a time.Duration	2019-10-31 16:12:07 +01:00
step_export.go	rename interpolation context from ctx to ictx and contexts to ctx to avoid conflicts	2019-04-03 15:56:15 +02:00
step_lxc_create.go	rename interpolation context from ctx to ictx and contexts to ctx to avoid conflicts	2019-04-03 15:56:15 +02:00
step_prepare_output_dir.go	rename interpolation context from ctx to ictx and contexts to ctx to avoid conflicts	2019-04-03 15:56:15 +02:00
step_provision.go	change Builder to be passed a context for cancellation	2019-04-03 15:55:55 +02:00
step_wait_init.go	rename interpolation context from ctx to ictx and contexts to ctx to avoid conflicts	2019-04-03 15:56:15 +02:00