stringify prefix for networks and not only its subnets #2629
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ee3379c to
f8efae3
Compare
47ef150 to
7a5b207
Compare
a-hassanin
requested changes
Oct 2, 2025
...ector/spec/unit/bosh/director/deployment_plan/network_planner/reservation_reconciler_spec.rb
Outdated
Show resolved
Hide resolved
aramprice
approved these changes
Oct 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
In the case of a vip network without subnets the prefix would not be stringified. This PR fixes it by pulling the to_s to the vip_network ensuring the prefix is always a string in the coding.