Dev/thekrauss/cloud instances with multiple network #1164
+268
−76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses issue #1115 by enabling the attachment of multiple private network interfaces to a Public Cloud instance.
Previously, the provider limited the network.private block to a single item (MaxItems: 1). This change allows users to define multiple private blocks to connect an instance to multiple vRacks/Subnets simultaneously (e.g., Front/Back architecture).
Type of change
• Schema: Changed network.private from TypeSet to TypeList to ensure interface ordering (eth1, eth2...) is respected and removed the MaxItems: 1 restriction.
• Structures: Updated Network struct to handle a slice of private networks ([]*PrivateNetwork) instead of a single pointer.
• Logic: Updated GetNetwork helper to iterate over all defined private blocks and construct the correct payload for the API