feat: upgrade terraform docs docker image version using renovate

[Monska85]

PR Type

Enhancement

---

Description

• Added automated version management for terraform-docs Docker image using Renovate
• Configured custom regex manager to track versions in Makefile
• Set up custom datasource integration with Quay.io repository
• Added new Makefile target for testing Renovate configuration locally

---

Changes walkthrough 📝

	Relevant files
Enhancement	Makefile Add Renovate configuration test target                                      Makefile Added new renovate-test target for testing Renovate configuration Test runs in Docker with debug logging and local platform simulation +9/-0
Configuration changes	renovate.json Configure Renovate for terraform-docs version management  renovate.json Added custom regex manager to track terraform-docs version in Makefile Configured custom datasource for Quay.io terraform-docs repository Set up version transformation templates for proper version handling +19/-3

---

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

[sparkfabrik-ai-bot]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 No relevant tests

🔒 Security concerns Container privilege escalation: The renovate-test Makefile target runs the container with root user privileges (-u "0:0"). This could potentially allow for container escape or host system access if the container is compromised. Consider running with least privilege principle using a non-root user.

⚡ Recommended focus areas for review Security Risk Running docker container with root user (0:0) in renovate-test target could pose security risks. Consider using a non-root user if possible. Validation Needed The JQ transformation template for API response should be validated to ensure it correctly parses all possible tag formats from Quay.io API

[sparkfabrik-ai-bot]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Avoid running Docker containers with root privileges to enhance security Running Docker with root privileges (-u "0:0") poses security risks. Consider using a non-root user or the current user ID like in the generate-docs target. Makefile [17-18] @docker run --rm -it \ - -u "0:0" \ + -u "$(id -u):$(id -g)" \ -e LOG_LEVEL=debug \ -v "$(PWD)":/tmp/app \ --entrypoint bash \ renovate/renovate Suggestion importance[1-10]: 9 Why: Running Docker containers as root (user 0) is a significant security risk. The suggestion to use the host user's ID, consistent with the generate-docs target, would significantly improve security while maintaining functionality.	9
Enhancement	Simplify JSON transformation pattern for better maintainability and readability The JQ transformation in the regex pattern could be simplified for better maintainability by using a more direct path selection. renovate.json [17-19] "transformTemplates": [ - "{ \"releases\": $map($.tags, function($v) { { \"version\": $v.name } }) }" + "{ \"releases\": [ { \"version\": .tags[].name } ] }" ] Suggestion importance[1-10]: 4 Why: While the suggested JQ transformation is more concise, the improvement is mainly cosmetic and both versions are functionally equivalent. The original version is already clear and working correctly.	4