-
Notifications
You must be signed in to change notification settings - Fork 77
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
fix: upgrade hcloud-go to v2 #1062
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1062 +/- ##
===========================================
+ Coverage 30.57% 66.43% +35.85%
===========================================
Files 67 69 +2
Lines 9951 9924 -27
===========================================
+ Hits 3043 6593 +3550
+ Misses 6868 2617 -4251
- Partials 40 714 +674
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
20a339d
to
73b3094
Compare
820d07c
to
1699bef
Compare
0551552
to
3f36288
Compare
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.
Looking through it I am hopeful for the future of hcloud-go
!
I am a bit worried about the naked int()
castings to downcast for terraform on 32 bit platforms. Go just does it, resulting in bad data. What do you think about adding a reverse function that converts from int64 to int on 64-bit platforms, and errors on 32-bit platforms?
53c7d44
to
6b1a1de
Compare
Yup, that's a sensible idea. I addressed your review comments and implement this for the relevant casts. |
This reverts commit b05b817.
7154355
to
c5a02ae
Compare
Attempt to migrate the hcloud-go library to v2, to be able to finally drop the v1 version.
We previously discussed of not going this route, but the effort of porting new features in both hcloud-go versions is bigger than upgrade the library in the terrafrom plugin.
If this change ends up being impossible to test and too dangerous, we will just continue the route we initially choose: migrating for to the plugin framework then the hcloud-go library.
Related to #877