-
Notifications
You must be signed in to change notification settings - Fork 20
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
feat: use existing IP for server create #144
feat: use existing IP for server create #144
Conversation
Co-authored-by: Julian Tölle <[email protected]>
Hey @sjagoe Ignore the acceptance tests, they cannot succeed on forks. Could you regenerate the docs? Using |
Co-authored-by: Jonas L. <[email protected]>
Co-authored-by: Jonas L. <[email protected]>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #144 +/- ##
==========================================
+ Coverage 27.28% 29.64% +2.35%
==========================================
Files 11 11
Lines 612 651 +39
==========================================
+ Hits 167 193 +26
- Misses 424 433 +9
- Partials 21 25 +4 ☔ View full report in Codecov by Sentry. |
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.
To be feature complete, the same for ipv6 should also be implemented.
I have implemented IP search by name, and IPv6. The plugin will still only use IPv4 to connect to the server, though. But there is still a case for assigning a static IPv6 to a server in any case (e.g. allowing the specific IPv6 address through a corporate firewall, for example). |
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.
I really appreciate that you are still sticking with us, we are almost done! Please address the last few comments on the tests, and maybe the lint errors will disappear.
Thanks!
Thanks, I appreciate your patience with me. This is the first Go I've written 😄 So building it up in small pieces was helpful to me anyway. Edit: Lint is happy now 🎉 thanks for the tips. |
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.
Awesome, I ran the integrations tests locally, all green!
Thanks again!
🤖 I have created a release *beep* *boop* --- ## [1.3.0](v1.2.1...v1.3.0) (2024-01-09) ### Features * add labels options to server and ssh keys ([#128](#128)) ([3f7dcae](3f7dcae)) * use existing IP for server create ([#144](#144)) ([1ebdfe7](1ebdfe7)) ### Bug Fixes * do not pass nil error to error handler ([#145](#145)) ([e742263](e742263)) * improve logs messages and error handling ([#139](#139)) ([2f2bcf1](2f2bcf1)) * improve missing hcloud token error ([#138](#138)) ([e47f476](e47f476)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This PR adds the ability to specify an existing Primary IP in the Hetzner Cloud project to be used for a packer build.
For short-lived IP addresses, Hetzner sometimes sends abuse notifications to the wrong IP address user.
To avoid this, for most things I run in Hetzner Cloud, I use pre-allocated Primary IPs, set to not auto-delete when the server is removed, so that I have easier tracking of IP address allocation to respond appropriately to Hetzner abuse notifications.