You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would be incredibly useful as it would allow Droplets to access the Floating IP during provisioning. I personally need this for a Consul deployment where each server node needs to advertise the address of its associated Floating IP. This allows me to effortlessly taint a failed server and simply let Terraform bring up a new one with same Floating IP and Volume attached as the old one.
Much like @miry, I'm envisioning something along the lines of:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 10, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Terraform v0.7.4
Affected Resource(s)
Please list the resources as a list, for example:
There are no example describes how to assign existing Float Ip resource to new droplet. https://www.terraform.io/docs/providers/do/r/floating_ip.html
It would great to have similar solution as for
aws_eip
: https://www.terraform.io/docs/providers/aws/r/eip_association.htmlExample:
or provide ip in
digitalocean_droplet
resource:The text was updated successfully, but these errors were encountered: