Skip to content

Merging to release-5.8: [TT-4023] Track 404 logs not showing in listening port when changing control api port (#7976)#8226

Merged
radkrawczyk merged 1 commit into
release-5.8from
merge/release-5.8/557c0fb6f7bb57108d5d7191783f9db49d8f0500/TT-4023
May 15, 2026
Merged

Merging to release-5.8: [TT-4023] Track 404 logs not showing in listening port when changing control api port (#7976)#8226
radkrawczyk merged 1 commit into
release-5.8from
merge/release-5.8/557c0fb6f7bb57108d5d7191783f9db49d8f0500/TT-4023

Conversation

@probelabs

@probelabs probelabs Bot commented May 15, 2026

Copy link
Copy Markdown
Contributor

TT-4023 Track 404 logs not showing in listening port when changing control api port (#7976)

Description

Related Issue

Motivation and Context

How This Has Been Tested

Screenshots (if appropriate)

Types of changes

  • 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

  • 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

Ticket Details

TT-4023
Status In Test
Summary Track 404 logs not showing in listening port when changing control api port

Generated at: 2026-05-15 09:20:51


Co-authored-by: Radosław Krawczyk [email protected]

…control api port (#7976)

<!-- Provide a general summary of your changes in the Title above -->

## Description

<!-- Describe your changes in detail -->

## Related Issue

<!-- 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

<!-- Why is this change required? What problem does it solve? -->

## How This Has Been Tested

<!-- 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

<!---TykTechnologies/jira-linter starts here-->

### Ticket Details

<details>
<summary>
<a href="https://tyktech.atlassian.net/browse/TT-4023" title="TT-4023"
target="_blank">TT-4023</a>
</summary>

|         |    |
|---------|----|
| Status  | In Test |
| Summary | Track 404 logs not showing in listening port when changing
control api port |

Generated at: 2026-05-15 06:36:31

</details>

<!---TykTechnologies/jira-linter ends here-->

---------

Co-authored-by: Radosław Krawczyk <[email protected]>
(cherry picked from commit 557c0fb)
@github-actions

Copy link
Copy Markdown
Contributor

🚨 Jira Linter Failed

Commit: 1720769
Failed at: 2026-05-15 09:20:52 UTC

The Jira linter failed to validate your PR. Please check the error details below:

🔍 Click to view error details
failed to validate Jira issue: jira ticket TT-4023 has status 'In Test' but must be one of: Dod Check, In Dev, In Code Review, Ready For Dev

Next Steps

  • Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
  • Verify your PR title matches the branch's Jira ticket ID
  • Check that the Jira ticket exists and is accessible

This comment will be automatically deleted once the linter passes.

@github-actions

Copy link
Copy Markdown
Contributor

Failed to generate code suggestions for PR

@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@radkrawczyk
radkrawczyk merged commit e7d435c into release-5.8 May 15, 2026
42 of 46 checks passed
@radkrawczyk
radkrawczyk deleted the merge/release-5.8/557c0fb6f7bb57108d5d7191783f9db49d8f0500/TT-4023 branch May 15, 2026 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants