Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to configure a Floating IP #278

Open
bobjohnbob opened this issue Apr 30, 2018 · 2 comments · May be fixed by #284
Open

Ability to configure a Floating IP #278

bobjohnbob opened this issue Apr 30, 2018 · 2 comments · May be fixed by #284

Comments

@bobjohnbob
Copy link

It would be nice to be able to specify (along with image/size/region) a floating IP to use on the droplet. Being created. When I setup a 'Vagrantfile' I typically make all these settings configurable via a file(along with a set of default settings). I would like to allow the developer to specify a floating IP(which is already provisioned and not assigned on the DO account) to attach to the droplet after it's up and running.

This is particularly useful for our application which requires a domain/subdomain be pointed to it to function properly (it's core to the functionality of the application) so that we don't have to change dns records and wait for TTL, or update /etc/host records each time we recreate the droplet.

If this is really easy to do and you can point me in the right direction, I can take a look at submitting a pull request, but my ruby experience it pretty rudimentary (I have only ever used it for editing "Vagrantfile"s)

@kwakwaversal kwakwaversal linked a pull request Mar 14, 2019 that will close this issue
@kwakwaversal
Copy link

I've opened a MR for this @bobjohnbob so hopefully it'll be merged in at some point. I patched my local copy a while ago and use it quite often - only just got around to pushing it upstream so it definitely works! 👍

@utkonos
Copy link

utkonos commented Nov 8, 2022

This would be a great feature. I want to note that the endpoints and DigitalOcean feature name is now "Private IP".

https://docs.digitalocean.com/reference/api/api-reference/#tag/Reserved-IP-Actions

The endpoints would then be changed from floating_ips to reserved_ips in the URL path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants