-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Adds the capability of provisioning with private ip for digitalocean #10093
Adds the capability of provisioning with private ip for digitalocean #10093
Conversation
Codecov Report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, this looks good! I'd love if you could add a couple of tests to the template logic, but otherwise I think this is good to merge.
…ct_with_private_ip
Thank you. Tests you want have been added. |
circle-ci complaining about changes at some files that are irrelevant with this pr. I re-cloned the repo and re-ran
|
I just reran the test suite and you're right it was some unrelated flake. Thanks for this contribution! |
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. |
Summary
connect_with_private_ip
to make provisioners to use the private ip instead of the public ip.vpc_uuid
for enabling the VPC UUID support that is presented by official DO APIOriginal problem
Packer is losing connection after provisioner creates a firewall rule that drops the ssh connections coming from outside of local network.
Done
make generate
make lint
displayed an error: