-
Notifications
You must be signed in to change notification settings - Fork 96
project: VPC Dual Stack #782
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
Conversation
b5419c3
to
584c930
Compare
@@ -520,7 +520,7 @@ func TestInstance_Disk_Clone(t *testing.T) { | |||
disk, err := client.CreateInstanceDisk(context.Background(), instance.ID, linodego.InstanceDiskCreateOptions{ | |||
Label: "go-disk-test-" + randLabel(), | |||
Filesystem: "ext4", | |||
Image: "linode/debian10", | |||
Image: "linode/debian12", |
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.
The changes made in this file aren't related to VPC Dual Stack but they were issues preventing me from re-running the instance fixtures.
assert.Equal(t, "auto", iface.Public.IPv4.Addresses[0].Address) | ||
} | ||
|
||
func TestInterface_Update(t *testing.T) { |
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.
TestInterface_Update
is redundant with the more granular interface update tests introduced in this PR, so I removed it for now 🙂
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.
This was a stale fixture file that's not longer referenced in an integration test.
* Add missing VPC Dual Stack docs and LA notices * Fix spacing
📝 Description
This pull request merges all changes relevant to the VPC Dual Stack branch into the
main
branch to stage it for release.Additionally, this PR contains refreshed fixtures for all
TestInstance*
,TestIPAddress*
,TestNodeBalancer*
, andTestVPC*
integration tests.✔️ How to Test
The following test steps assume you have pulled down this PR locally and are using a Linode account with access to VPC Dual Stack.
Unit Testing
Integration Testing