-
Notifications
You must be signed in to change notification settings - Fork 0
removing function AnalyzeNACLRules and fix tests #932
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
Conversation
this branch is included in #933 |
fmt.Printf("ipBlockString: %v\n", ipBlockString) | ||
fmt.Printf("connectivityResult.AllowedConns: \n") | ||
for ipRange, conn := range connectivityResult.AllowedConns { | ||
fmt.Printf("ipRange.ToIPRanges(): %v\n", ipRange.ToIPRanges()) | ||
fmt.Printf("conn: %v\n", conn) | ||
} | ||
|
||
//nolint:all | ||
/*src := common.FromCidr("1.1.1.1/32") | ||
dst := common.FromCidr("10.0.0.0/24") | ||
disjointPeers := []*netset.IPBlock{dst} | ||
res := commonvpc.GetAllowedXgressConnections(rulesTest1, src, dst, disjointPeers, true) | ||
for d, c := range res { | ||
fmt.Printf("%s => %s : %s\n", src.ToIPAdress(), d, c.String()) | ||
require.True(t, c.Equal(getAllConnSet())) | ||
}*/ | ||
fmt.Printf("connectivityResult.AllowRules: \n") | ||
for ipRange, conn := range connectivityResult.AllowRules { | ||
fmt.Printf("ipRange.ToIPRanges(): %v\n", ipRange.ToIPRanges()) | ||
fmt.Printf("conn: %v\n", conn) | ||
} | ||
fmt.Printf("connectivityResult.DeniedConns: \n") | ||
for ipRange, conn := range connectivityResult.DeniedConns { | ||
fmt.Printf("ipRange.ToIPRanges(): %v\n", ipRange.ToIPRanges()) | ||
fmt.Printf("conn: %v\n", conn) | ||
} | ||
|
||
fmt.Printf("done\n") | ||
fmt.Printf("connectivityResult.DenyRules: \n") | ||
for ipRange, conn := range connectivityResult.DenyRules { | ||
fmt.Printf("ipRange.ToIPRanges(): %v\n", ipRange.ToIPRanges()) | ||
fmt.Printf("conn: %v\n", conn) | ||
} |
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.
Do we need all these prints?
We already have huge logs for our tests - it makes it hard to search for failures.
So unless there is a failure, I prefer tests to produce only very little text if at all.
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.
not needed
removed
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.
in #933
No description provided.