Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[TT-9504] Moving AddTraceID call to ProcessRequest function (TykTechn…
…ologies#5425) <!-- Provide a general summary of your changes in the Title above --> ## Description Moving AddTraceID call to ProcessRequest function in order to write the header no matter if the request to the upstream was made or not (i.e. 4xx cases, which fail because of authentication issues) <!-- Describe your changes in detail --> ## Related Issue https://tyktech.atlassian.net/jira/software/c/projects/TT/boards/42?selectedIssue=TT-9464 <!-- This project only accepts pull requests related to open issues. --> <!-- If suggesting a new feature or change, please discuss it in an issue first. --> <!-- If fixing a bug, there should be an issue describing it with steps to reproduce. --> <!-- OSS: Please link to the issue here. Tyk: please create/link the JIRA ticket. --> ## Motivation and Context https://tyktech.atlassian.net/jira/software/c/projects/TT/boards/42?selectedIssue=TT-9464 <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested Manual testing (based on this Loom video: https://www.loom.com/share/d43ed2aa81b843f5908e5b39a09033e7?sid=5c59e225-6dd1-4ac1-9a2e-80f35a2752ab) and unit tests were already created for this function <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why
- Loading branch information