Fix left overs from PR#1564#1574
Merged
iaftab-alam merged 1 commit intocloudfoundry:developfrom May 22, 2025
Merged
Conversation
iaftab-alam
force-pushed
the
fix-Ipv6-group-leftovers
branch
from
361eb7a to
547c641
Compare
iaftab-alam
force-pushed
the
fix-Ipv6-group-leftovers
branch
from
547c641 to
42b8136
Compare
jochenehret
approved these changes
May 22, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Are you submitting this PR against the develop branch?
What is this change about?
There were some left overs from PR. This PR aim to fix this.
Please provide contextual information.
The existing go lang app was changed with this PR that introduces new group and made changes to already existing check, which needs to be propagated where is is consumed.
What version of cf-deployment have you run this cf-acceptance-test change against?
N/A
Please check all that apply for this PR:
Did you update the README as appropriate for this change?
How many more (or fewer) seconds of runtime will this change introduce to CATs?
N/A
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
It's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.