[SYSE-370 release-5.3] June template application

[ermirizio]

User description

• [ ] Images not being pushed to dockerhub on tag when distroless feature is missing
• [ ] Policy match fix
• [ ] Fix github ref name for test-controller ui on push trigger
• [x] Test controller UI missing conf for push event and other missconfigs
• [x] Test controller UI duplicated lines under pump & sink
• [ ] Quality gates for tyk-analitycs UI and API regression tests
• [x] release-5.3 is not treated correctly in test-controller logic
• [ ] Implement custom rules for enterprise artifacts in package promotion
• [x] Test controller UI
• [x] Accomodate templates for new controller UI
• [x] Add mongo7 and redis7 with cache_DB config field

---

PR Type

Enhancement, Bug fix

---

Description

• Added Docker metadata action for tag push to ensure images are correctly tagged and labeled.
• Simplified and corrected the usage of the BASE_REF environment variable to use github.ref_name.
• Updated Docker build and push steps with new configurations for multiarch image building and SBOM generation.
• Fixed issues with GitHub ref name handling in test-controller logic to ensure proper environment setup and testing.

---

Changes walkthrough 📝

	Relevant files
Enhancement	release.yml Enhance Docker metadata and fix BASE_REF handling in release workflow .github/workflows/release.yml Added Docker metadata action for tag push. Simplified and corrected BASE_REF environment variable usage. Updated Docker build and push steps with new configurations. Fixed issues with GitHub ref name handling in test-controller logic. +34/-25

---

💡 PR-Agent usage: Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions[bot]]

PR Reviewer Guide 🔍

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ Key issues to review **Possible Bug:** The PR introduces changes in the handling of the BASE_REF environment variable to use `github.ref_name` instead of `github.ref`. This change appears in multiple places and could potentially affect how environments are set up for different GitHub events. It's crucial to ensure that this change is thoroughly tested across all scenarios where BASE_REF is used. **Configuration Consistency:** The PR adds new Docker metadata and build-push configurations. It's important to verify that these configurations are consistent with existing CI/CD pipelines and do not introduce any discrepancies that could affect the build or deployment processes.

[github-actions[bot]]

API Changes

no api changes detected

[github-actions[bot]]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	Improve the accuracy of the BASE_REF assignment by using a more specific conditional logic ___ **Replace the direct usage of github.ref_name with a more specific conditional check to ensure that the correct reference is used in different GitHub event contexts. This prevents potential issues where the wrong reference could be used, leading to incorrect behavior in CI workflows.** [.github/workflows/release.yml [211]](https://github.com/TykTechnologies/tyk/pull/6404/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34R211-R211) ```diff -BASE_REF: ${{startsWith(github.event_name, 'pull_request') && github.base_ref || github.ref_name}} +BASE_REF: ${{ github.event_name == 'pull_request' ? github.base_ref : github.ref_name }} ``` Suggestion importance[1-10]: 9 Why: The suggestion improves the accuracy of the BASE_REF assignment by using a more explicit conditional check, which enhances the reliability of the CI workflow. This change is crucial for ensuring correct behavior in different GitHub event contexts.	9
Best practice	Add error handling to the Docker run command to improve robustness ___ **Add error handling for the Docker run command to manage failures gracefully and provide more informative error messages, enhancing the robustness of the CI pipeline.** [.github/workflows/release.yml [284]](https://github.com/TykTechnologies/tyk/pull/6404/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34R284-R284) ```diff -docker run -q --rm -v ~/.docker/config.json:/root/.docker/config.json tykio/gromit policy match ${match_tag} 2>versions.env +docker run -q --rm -v ~/.docker/config.json:/root/.docker/config.json tykio/gromit policy match ${match_tag} 2>versions.env || echo "Error: Docker run failed for policy match" ``` Suggestion importance[1-10]: 8 Why: Adding error handling to the Docker run command improves the robustness of the CI pipeline by providing informative error messages and managing failures gracefully. This is a best practice that enhances the reliability of the workflow.	8
Enhancement	Harmonize the cache settings in Docker actions to enhance efficiency ___ **Ensure that the Docker cache-from and cache-to types are consistently set to the same mode to optimize the caching mechanism and avoid potential inconsistencies that can lead to longer build times or cache misses.** [.github/workflows/release.yml [177-178]](https://github.com/TykTechnologies/tyk/pull/6404/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34R177-R178) ```diff -cache-from: type=gha +cache-from: type=gha,mode=max cache-to: type=gha,mode=max ``` Suggestion importance[1-10]: 7 Why: The suggestion ensures consistent cache settings, which can optimize the caching mechanism and potentially reduce build times. This is a good enhancement for efficiency but not critical.	7

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud