private_networking = false, seems to be ignored

[cameronelliott]

Describe the bug

Creating an instance with private_networking = false appears to have the private networking enabled anyway,
both in reality and in the terraform show output.
I'm sorta new to Terraform, so if this is somehow a user mistake (or my mistake), my apologies.

Affected Resource(s)

• digitalocean_droplet

Expected Behavior

I would think the output of terraform show|grep priv would show that private networking would be false, not true, given the apply preview and the .tf file show private_networking = false.

Actual Behavior

terraform show indicates that private networking was enabled.

[email protected] ~/D/t/d/bug> terraform show|grep priv
    ipv4_address_private = "10.132.0.3"
    private_networking   = true
[email protected] ~/D/t/d/bug>

Steps to Reproduce

terraform init
terraform apply -var "do_token=$DIGITALOCEAN_ACCESS_TOKEN" -var "pvt_key=$HOME/.ssh/id_rsa" -auto-approve

Full log at gist link, with .tf files.

Terraform Configuration Files
https://gist.github.com/cameronelliott/9ef23e442572891937b0ed1c0c843f3f

Terraform version

[email protected] ~/D/t/d/bug> terraform -v
Terraform v1.0.5
on darwin_amd64
+ provider registry.terraform.io/digitalocean/digitalocean v2.11.1
[email protected] ~/D/t/d/bug>

Captured log Output
https://gist.github.com/cameronelliott/9ef23e442572891937b0ed1c0c843f3f

[danaelhe]

Hi there,

Thanks for reaching out. The private_networking has been marked deprecated and vpc_uuid should be used instead to specify a VPC network for the Droplet. This has been stated here, but I can see how that documentation is not obvious to check for, so I will update the API docs and mark the attribute as deprecated in the schema definition. Thanks for bringing this to our attention.