-
Notifications
You must be signed in to change notification settings - Fork 47
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: (CXF 90011) Updating Metal & Fabric Provider with NIMF functionality #626
Conversation
srushti-patl
commented
Mar 22, 2024
•
edited
Loading
edited
- Added authorization_code to metal_interconnection schema.
- Added buildSharedPortVCVLANCreateRequest() function for the connection type shared_port_vlan request.
- Added DataSource and Resource Acc Tests for Vlan Port Share functionality.
- Added "METAL_NETWORK" to Fabric connection Access Point Type schema
- Updated Fabric Go SDK Version to 0.9.0
…ource with sharedPort request
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #626 +/- ##
===========================================
+ Coverage 38.00% 60.96% +22.95%
===========================================
Files 120 120
Lines 19428 19476 +48
===========================================
+ Hits 7384 11873 +4489
+ Misses 11836 7034 -4802
- Partials 208 569 +361 ☔ View full report in Codecov by Sentry. |
IMO this should have the |
resource.TestCheckResourceAttr( | ||
"equinix_metal_connection.test", "metro", "sv"), | ||
resource.TestCheckResourceAttr( | ||
"equinix_metal_connection.test", "contact_email", "tfacc@example.com"), |
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.
Should we test that the authorization_code
is populated here?
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 have added authorization_code parameter check in acc tests
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.
Will there be a related PR for the Metal2SpAws
create body on the Fabric /connections API?
We have included the required Fabric Provider changes in this PR only. There is only one change required in the Fabric Provider to support NIMF functionality. |
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.
LGTM for Fabric changes. Metal side looks good as well but leaving that for those who have more familiarity with the product side of things.
might need a rebase, but LGTM |
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 had one question about the fabric-go upgrade, and I don't see the changes Adam suggested for testing that the authorization_code attribute has a value.
…o CXF-90011-Metal-NIMF-Update
I have upgraded fabric-go-sdk version to 0.9.0 and I have already added authorization_code parameter check in metal connection resource and data source acc tests with TestCheckResourceAttrSet() function as authorization_code's value is dynamic. |
@ctreatma I see it now, the addition of |
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.
LGTM, though there are some failing acceptance tests
@adammohammed how can we add the CI user to the allow list for NIMF? |
@ctreatma on it. @srushti-patl the CI organization should have this feature available to it now. We should be able to re-run the tests. |
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 see the new tests passing in run #2 of the Metal acceptance tests. Test failures are all in unrelated tests due to platform capacity ("no available servers in metro"), or tests using recently-disabled features ("facility is not supported"), or tests that are known to flake (spot market tests).