-
Notifications
You must be signed in to change notification settings - Fork 592
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
Trigger Reply Tracing #949
Conversation
The following is the coverage report on pkg/.
|
for n, v := range tctx.Header { | ||
lower := strings.ToLower(n) | ||
if forwardHeaders.Has(lower) { | ||
sendingCTX = addHeader(sendingCTX, n, v) | ||
h[n] = v |
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.
Why not use the h.Add here?
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.
h.Add
only works with an individual string
and value is []string
. Using h.Add
, I would need to do a for loop:
for _, iv := range v {
h.Add(n, iv)
}
continue | ||
} | ||
for _, prefix := range forwardPrefixes { | ||
if strings.HasPrefix(lower, prefix) { | ||
sendingCTX = addHeader(sendingCTX, n, v) | ||
h[n] = v |
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.
ditto.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Harwayne, vaikas-google The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Reimplementing fetching of wathola report with K8s job This change targets the problem of how to get report from cluster. Clusters may have different networking setup, and it might not be possible to directly make HTTP request from outside of cluster. Previous approach used to guess an external address of cluster. That for sure fails on OpenShift deployed on AWS. This approach deploys a special Job that, being inside cluster, can download a report and print it in it's logs. Then test client can fetch logs of completed job, and parse it, replay the logs, and process report further. Removal of unneeded external node address package * wathola-fetcher test image * Adding a tip of how to override openshift/release repo location
Proposed Changes
Release Note