712b3e74b6
The second step of the `TestAccDigitalOceanDroplet_ResizeWithOutDisk` acceptance test was regularly failing. Upon investigation it was found that the second step's Terraform configuration had omitted the `user_data` parameter, thus forcing Terraform to create a new droplet resource instead of updating the current resource.
```
-/+ digitalocean_droplet.foobar
disk: "20" => "<computed>"
image: "centos-7-x64" => "centos-7-x64"
ipv4_address: "138.197.0.55" => "<computed>"
ipv4_address_private: "" => "<computed>"
ipv6_address: "" => "<computed>"
ipv6_address_private: "" => "<computed>"
locked: "false" => "<computed>"
name: "foo" => "foo"
region: "nyc3" => "nyc3"
resize_disk: "true" => "false"
size: "512mb" => "1gb"
ssh_keys.#: "1" => "1"
ssh_keys.0: "5770472" => "5770472"
status: "active" => "<computed>"
user_data: "foobar" => "" (forces new resource)
vcpus: "1" => "<computed>"
```
This fixes the acceptance test by adding the missing `user_data` parameter.
|
||
|---|---|---|
| .. | ||
| config.go | ||
| import_digitalocean_domain_test.go | ||
| import_digitalocean_droplet_test.go | ||
| import_digitalocean_floating_ip_test.go | ||
| import_digitalocean_ssh_key_test.go | ||
| import_digitalocean_tag_test.go | ||
| import_digitalocean_volume_test.go | ||
| provider.go | ||
| provider_test.go | ||
| resource_digitalocean_domain.go | ||
| resource_digitalocean_domain_test.go | ||
| resource_digitalocean_droplet.go | ||
| resource_digitalocean_droplet_test.go | ||
| resource_digitalocean_floating_ip.go | ||
| resource_digitalocean_floating_ip_test.go | ||
| resource_digitalocean_record.go | ||
| resource_digitalocean_record_test.go | ||
| resource_digitalocean_ssh_key.go | ||
| resource_digitalocean_ssh_key_test.go | ||
| resource_digitalocean_tag.go | ||
| resource_digitalocean_tag_test.go | ||
| resource_digitalocean_volume.go | ||
| resource_digitalocean_volume_test.go | ||
| tags.go | ||
| tags_test.go | ||