Skip to content

Migration from floating to reserved IPs #844

Answered by andrewsomething
bheisig asked this question in Q&A
Discussion options

You must be logged in to vote

If you are using v2.21.0 of the provider, the digitalocean_floating_ip resource has been updated to use the api.digitalocean.com/v2/reserved_ips endpoints under the hood. So no immediate action is needed. That said, we will likely deprecate it at some point in the future to reduce code duplication and prevent new users from mistakenly choosing the wrong resource.

Starting from a config like:

resource "digitalocean_floating_ip" "foobar" {
  region = "nyc1"
}

resource "digitalocean_droplet" "foobar" {
  name               = "foobar"
  size               = "s-1vcpu-1gb"
  image              = "ubuntu-20-04-x64"
  region             = "nyc1"
}

resource "digitalocean_floating_ip_assignment" "…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by bheisig
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants