-
Notifications
You must be signed in to change notification settings - Fork 260
Use flag set.Func() instead of custom type for -H #999
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
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #999 +/- ##
========================================
- Coverage 73.9% 73.9% -0.1%
========================================
Files 25 25
Lines 6205 6200 -5
========================================
- Hits 4587 4580 -7
Misses 1450 1450
- Partials 168 170 +2 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
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.
Thanks ! there are more in fortio_main for the proxies too - can you change these too please?
and did you manually test to confirm it works the same?
|
I don’t remember if I do have a test for multiple headers through CLI using the echo from debug.fortio.org for instance, maybe should add such txtar test if there isn’t. basically that multiple (and single) -H still works , ditto for proxies etc |
this does test the multiple -H https://github.com/fortio/fortio/blob/master/cli_test.txtar#L21 but for proxies not sure we have a test outside of https://github.com/fortio/fortio-demo-chart/blob/main/helm/fortio/templates/fortio.yaml#L205-L208 but that chart is used but not part of tests |
Add tests to cli_test.txtar file for the flags |
did a manual test to confirm -M
-P
|
fix #993
fix #1000