Complete rewrite of the module to deploy a Renovate bot for automated dependency management with Gitea integration. Breaking Changes: - Module purpose changed from Ansible EDA to Renovate bot - All variables restructured for Renovate configuration - State file path updated to home/docker/renovate/renovate.tfstate - Volumes changed from EDA rulebooks/logs to config/cache - Container image now uses renovate/renovate:latest Added: - Gitea platform integration with token authentication - Renovate configuration template (config.js.tpl) - Repository configuration examples - Gitea Actions workflow examples - SonarQube integration examples - Comprehensive documentation (README, QUICKSTART, MIGRATION_GUIDE) - CHANGELOG.md for version tracking - Security best practices Removed: - All Ansible EDA-specific configuration - Traefik labels (not needed for Renovate) - Old EDA documentation files - example-rulebook.yml Updated: - Complete README with Gitea setup instructions - terraform.tfvars with Renovate configuration - All resource names from ansible_eda to renovate - Backend state path This is version 2.0.0 - not backward compatible with previous EDA version. See MIGRATION_GUIDE.md for detailed migration instructions.
2.9 KiB
2.9 KiB
Changelog
All notable changes to this Terraform module will be documented in this file.
[2.0.0] - 2024-11-17
Changed - Major Refactoring
This module has been completely repurposed from Ansible EDA to Renovate bot deployment.
Breaking Changes
- Module Purpose: Changed from Ansible Event-Driven Automation to Renovate bot deployment
- Container Image: Now uses
renovate/renovate:latestinstead ofquay.io/ansible/ansible-rulebook:latest - Volumes: Replaced
ansible-eda-rulebooksandansible-eda-logswithrenovate-configandrenovate-cache - Variables: Complete restructure of variables to support Renovate configuration
- Configuration: Now uses
config.jstemplate instead of YAML rulebooks - State Path: Updated from
home/docker/ansible-eda/ansible-eda.tfstatetohome/docker/renovate/renovate.tfstate
Added
- Renovate bot container deployment with Gitea integration
config.js.tpltemplate for automated configurationexample-renovate.jsonfor repository-level configurationexample-gitea-workflow.yamlfor CI/CD integration- New variables:
renovate_platform- Git platform (gitea, github, gitlab)renovate_endpoint- API endpoint URLrenovate_token- Bot authentication tokenrenovate_git_author- Git commit authorrenovate_username- Bot usernamerenovate_autodiscover- Auto-discover repositoriesrenovate_onboarding_config- Onboarding configurationgithub_com_token- Optional GitHub.com tokenupload_config_file- Control config.js uploadrestart_policy- Container restart policy
- Comprehensive README with Gitea setup instructions
- SonarQube integration examples
- Pipeline configuration examples
- Security best practices documentation
Removed
- All Ansible EDA-specific configuration
rulebook_commandvariablewebhook_portvariableupload_example_rulebookvariableexample-rulebook.ymlfile- Traefik labels (Renovate doesn't need web access)
- Old documentation files:
MIGRATION_SUMMARY.mdDECISION_POINTS.mdIMPLEMENTATION_PLAN.md
Updated
- README.md with complete Renovate documentation
- terraform.tfvars with Renovate-specific configuration
- All resource names from
ansible_edatorenovate - Output variables to reflect new purpose
- Security considerations for Renovate bot
Migration Notes
If you were using the previous Ansible EDA version:
- This is a complete rewrite - not backward compatible
- State file path has changed - plan accordingly
- All volumes will be recreated
- Variable names have completely changed
- Consider creating a new module instance rather than migrating
[1.0.0] - 2024-11-16
Initial Release (Ansible EDA)
- Initial Terraform module for Ansible Event-Driven Automation
- Docker container deployment with Traefik integration
- Vault authentication for DNS credentials
- MinIO backend for state storage
- Resource limits and persistent volumes