[WIP/Testing] Import service discovery CI test

[titpetric]

PR Type

Tests, Enhancement

---

Description

• Added a new CI test setup for service discovery.

• Introduced Taskfile.yml for managing test tasks and environment.

• Configured docker-compose.yml for service discovery testing.

• Added tyk.conf for gateway configuration in service discovery tests.

---

Changes walkthrough 📝

	Relevant files
Documentation	README.md Documented service discovery test setup and tasks                ci/tests/service-discovery/README.md Added a README file for service discovery tests. Listed current state and future tasks for service discovery. +15/-0
Configuration changes	Taskfile.yml Added task management for service discovery tests                ci/tests/service-discovery/Taskfile.yml Added task definitions for managing the test environment. Included tasks for building, pulling, and running Docker containers. Added tasks for checking environment status and logs. +47/-0    docker-compose.yml Configured Docker Compose for service discovery                    ci/tests/service-discovery/docker-compose.yml Configured Docker Compose for service discovery tests. Included external services like Redis and Httpbin. Defined the tyk service with necessary configurations. +21/-0    tyk.conf Added gateway configuration for service discovery                ci/tests/service-discovery/tyk.conf Added gateway configuration for service discovery tests. Configured Redis storage and HTTP server options. Included analytics and DNS cache settings. +43/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about PR-Agent usage.

Check out the documentation for more information.

[buger]

A JIRA Issue ID is missing from your branch name, PR title and PR description! 🦄

Your branch: test/service-discovery

Your PR title: [WIP/Testing] Import service discovery CI test

Your PR description: null

If this is your first time contributing to this repository - welcome!

---

Please refer to jira-lint to get started.

Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail.

Valid sample branch names:

‣ feature/shiny-new-feature--mojo-10'
‣ 'chore/changelogUpdate_mojo-123'
‣ 'bugfix/fix-some-strange-bug_GAL-2345'

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 No relevant tests

🔒 Security concerns Sensitive information exposure: The hardcoded secret field in tyk.conf could lead to unauthorized access if exposed. It is recommended to use environment variables or a secure secrets management system to handle sensitive data.

⚡ Recommended focus areas for review Possible Misconfiguration The rm -rf src/ command in the default task could potentially delete unintended files or directories if the src path is not properly validated. This should be reviewed for safety. - rm -rf src/ Hardcoded Secret The secret field in the tyk.conf file contains a hardcoded value. This could pose a security risk and should be replaced with a dynamically generated or environment-based value. "secret": "352d20ee67be67f6340b4c0605b044b7",

[github-actions]

API Changes

no api changes detected

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Secure sensitive configuration values Replace the hardcoded secret value with an environment variable or a secure secrets management solution to avoid exposing sensitive information in the configuration file. ci/tests/service-discovery/tyk.conf [4] -"secret": "352d20ee67be67f6340b4c0605b044b7", +"secret": "${TYK_SECRET}", Suggestion importance[1-10]: 10 Why: Replacing the hardcoded secret with an environment variable enhances security by preventing sensitive information from being exposed in the configuration file. This is a critical improvement for secure application deployment.	10
Possible issue	Add validation to prevent accidental deletions Add error handling or validation for the rm -rf src/ command in the default task to prevent accidental deletion of unintended directories or files. ci/tests/service-discovery/Taskfile.yml [8] -- rm -rf src/ +- test -d src/ && rm -rf src/ Suggestion importance[1-10]: 9 Why: Adding validation to the rm -rf src/ command significantly reduces the risk of accidental deletions, which could cause unintended data loss. The suggestion is accurate and directly improves the safety of the script.	9

[sonarqubecloud]

Quality Gate passed

Issues
7 New issues
0 Accepted issues

Measures
0 Security Hotspots
83.5% Coverage on New Code
0.2% Duplication on New Code

See analysis details on SonarQube Cloud