Update N8N module with latest changes.

Change Summary

This git diff primarily focuses on updating configurations and dependencies within the project. Key changes include updating pre-commit hooks, modifying Terraform configurations for an n8n application, and updating provider versions in Terraform lock files.

Technical Details

• .pre-commit-config.yaml:
  • Replaced terraform-fmt with tofu-fmt to align with the latest tooling standards.
• IaC/modules/n8n/main.tf:
  • Updated the ArgoCD application configuration for the n8n module.
  • Changed the target revision from 1.0.10 to 2.0.x.
  • Updated the n8n image tag from 1.102.4 to 1.122.x.
  • Modified the ingress configuration to include className and updated paths to use ImplementationSpecific.
• IaC/production/homelab/n8n/.terraform.lock.hcl:
  • Updated the version and constraints of the ArgoCD provider from 7.12.3 to 7.12.4.

Key Learnings & Insights

• The switch from terraform-fmt to tofu-fmt indicates a migration or update in the tooling used for formatting Terraform files, suggesting a move towards newer or more standardized tools.
• Updating the n8n application to a newer version (2.0.x) and image tag (1.122.x) likely aims to incorporate the latest features, bug fixes, and security patches.
• The ingress configuration changes reflect an adaptation to newer Kubernetes ingress class specifications, enhancing compatibility and potentially improving routing efficiency.
• Updating provider versions in Terraform lock files ensures that the infrastructure code uses the latest provider features and bug fixes, maintaining system reliability and security.

Impact Assessment

• These changes should result in a more up-to-date and secure infrastructure setup.
• The update to the n8n application and image may introduce new features or behaviors, requiring testing to ensure compatibility with existing workflows.
• The ingress configuration changes might affect routing rules and should be verified in the staging environment before production deployment.

Developer Notes

• Ensure that all dependencies and provider versions are compatible with the updated configurations.
• Test the new n8n version and image tag in a staging environment to identify any potential issues before deploying to production.
• Review the ingress configuration changes to confirm they align with the expected routing behavior and security requirements.
• Consider documenting the reasoning behind the tooling changes (e.g., terraform-fmt to tofu-fmt) for future reference.