Merging to release-5.7: [TT-13658] added missing logger from provider initialisation (#6729)

[buger]

User description

TT-13658 added missing logger from provider initialisation (#6729)

User description

TASK: https://tyktech.atlassian.net/browse/TT-13658

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

---

PR Type

Bug fix

---

Description

• Added a missing logger to the Provider initialization in the upstreamoauth middleware.
• This change ensures that logging is properly configured, preventing potential issues related to missing logs.

---

Changes walkthrough 📝

	Relevant files
Bug fix	middleware.go Add missing logger to Provider initialization                        ee/middleware/upstreamoauth/middleware.go Added a missing logger to the Provider initialization. Ensures that the Logger is properly set in the upstreamOAuthProvider. +1/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

---

PR Type

Bug fix

---

Description

• Added a missing logger to the Provider initialization in the upstreamoauth middleware.
• This change ensures that logging is properly configured, preventing potential issues related to missing logs.

---

Changes walkthrough 📝

	Relevant files
Bug fix	middleware.go Add missing logger to Provider initialization                        ee/middleware/upstreamoauth/middleware.go Added a missing logger to the Provider initialization. Ensures that the Logger is properly set in the upstreamOAuthProvider. +1/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions[bot]]

API Changes

no api changes detected

[github-actions[bot]]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

**🎫 Ticket compliance analysis ✅** **[6729](https://github.com/TykTechnologies/tyk/issues/6729) - Fully compliant** Fully compliant requirements: - Added a missing logger to the Provider initialization in the upstreamoauth middleware.

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[github-actions[bot]]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Prevent potential nil pointer dereference by ensuring the Logger is initialized ___ **Ensure that the Logger field is properly initialized in the Provider struct to avoid nil pointer dereference when the Logger method might return nil.** [ee/middleware/upstreamoauth/middleware.go [83]](https://github.com/TykTechnologies/tyk/pull/6730/files#diff-1347b256f3728407a2697f1e824391eaa329162e644741d8321f25c7a0630363R83-R83) ```diff -Logger: m.Logger(), +Logger: m.Logger(), // Ensure Logger is not nil ``` Suggestion importance[1-10]: 7 Why: The suggestion is relevant as it addresses a potential runtime error (nil pointer dereference) which is critical in ensuring the robustness of the application. However, the improved code does not implement a check but only adds a comment, which does not prevent the issue but raises awareness. A runtime check would be more effective.	7

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud