You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After releasing v1.2.3 containing a change to the step_network_info.go for subnet selection when using associate_public_ip_address with no subnet_id or vpc_id set users encountered a regression with subnet selection no longer working as expected. To test the regression fix a set of acceptance tests were added with different scenarios for subnet selection. While the test do represent the issues reported it would be better suited to have a suite of unit tests that can validate the expected functionality.
The lack of tests for the complicated code base is considered a bug that we need to fix.
Overview of the Issue
After releasing v1.2.3 containing a change to the step_network_info.go for subnet selection when using
associate_public_ip_address
with nosubnet_id
orvpc_id
set users encountered a regression with subnet selection no longer working as expected. To test the regression fix a set of acceptance tests were added with different scenarios for subnet selection. While the test do represent the issues reported it would be better suited to have a suite of unit tests that can validate the expected functionality.The lack of tests for the complicated code base is considered a bug that we need to fix.
Related Changes
The text was updated successfully, but these errors were encountered: