packer-cn/builder/digitalocean
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 Add DigitalOcean post-processor. 2018-11-29 21:00:57 -05:00
artifact_test.go Fix tests and add more 2017-05-16 21:00:13 -07:00
builder.go Change back to make sure all durations are a time.Duration 2019-10-31 16:12:07 +01:00
builder_acc_test.go move packer to hashicorp 2017-04-04 13:39:01 -07:00
builder_test.go Change back to make sure all durations are a time.Duration 2019-10-31 16:12:07 +01:00
config.go Change back to make sure all durations are a time.Duration 2019-10-31 16:12:07 +01:00
config.hcl2spec.go commit old code generation tool 2019-10-15 12:56:42 +02:00
step_create_droplet.go rename interpolation context from ctx to ictx and contexts to ctx to avoid conflicts 2019-04-03 15:56:15 +02:00
step_create_ssh_key.go rename interpolation context from ctx to ictx and contexts to ctx to avoid conflicts 2019-04-03 15:56:15 +02:00
step_droplet_info.go Change back to make sure all durations are a time.Duration 2019-10-31 16:12:07 +01:00
step_power_off.go Change back to make sure all durations are a time.Duration 2019-10-31 16:12:07 +01:00
step_shutdown.go Change back to make sure all durations are a time.Duration 2019-10-31 16:12:07 +01:00
step_snapshot.go builder/digitalocean: add snapshotTimeout option 2019-07-04 16:25:42 +02:00
token_source.go builder/digitalocean: switch to new lib 2015-06-10 14:02:06 -07:00
wait.go Add DigitalOcean post-processor. 2018-11-29 21:00:57 -05:00