-
Notifications
You must be signed in to change notification settings - Fork 665
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
internal/dag: Filter on Gateway.Listener.Protocol for supported types #3612
internal/dag: Filter on Gateway.Listener.Protocol for supported types #3612
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3612 +/- ##
==========================================
+ Coverage 76.66% 76.69% +0.02%
==========================================
Files 100 100
Lines 7066 7075 +9
==========================================
+ Hits 5417 5426 +9
+ Misses 1533 1532 -1
- Partials 116 117 +1
|
Filters the Protocol on gateway listeners for only valid types (e.g. HTTP, HTTPS, TLS). Fixes projectcontour#3540 Signed-off-by: Steve Sloka <slokas@vmware.com>
2f2950d
to
0ec52fe
Compare
internal/dag/builder_test.go
Outdated
Spec: gatewayapi_v1alpha1.GatewaySpec{ | ||
Listeners: []gatewayapi_v1alpha1.Listener{{ | ||
Port: 443, | ||
Protocol: gatewayapi_v1alpha1.HTTPProtocolType, // <--- invalid protocol, must be "HTTPS" |
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.
is this comment removable/movable to the below test case?
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.
or maybe the test case names got mixed up? looking at the full file it looks like this test case is actually "insert basic single route, single hostname, gateway with TLS, invalid listener protocol"
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'll remove the comment since now the protocol is ignored in relation to if tls is defined or not.
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.com>
Signed-off-by: Steve Sloka <slokas@vmware.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.
LGTM pending CI.
Filters the Protocol on gateway listeners for only valid types (e.g. HTTP, HTTPS, TLS).
Fixes #3540
Signed-off-by: Steve Sloka slokas@vmware.com