Update Octobot module image version.

Change Summary

This git diff involves a minor but significant update to the main.tf file within the IaC/modules/octobot directory. The change updates the version specification for the octobot Argo CD application, transitioning from a fixed minor version (2.0.x) to a more flexible major version range (2.x).

Technical Details

• File: IaC/modules/octobot/main.tf
• Change: Updated the annotation for the argocd_application resource.
  • Before: "argocd-image-updater.argoproj.io/image-list" = "octobot=drakkarsoftware/octobot:2.0.x"
  • After: "argocd-image-updater.argoproj.io/image-list" = "octobot=drakkarsoftware/octobot:2.x"
• This change allows the Argo CD image updater to pull any version within the 2.x range, rather than being restricted to the 2.0.x minor version.

Key Learnings & Insights

• Reasoning: The change was made to provide greater flexibility in the deployment process. By allowing any 2.x version, the system can benefit from newer minor versions that may include bug fixes, security patches, and features without requiring manual updates to the Terraform configuration.
• Problem-Solving Approach: The team identified a need for more agility in managing dependencies. This update ensures that the deployment pipeline can automatically incorporate newer, compatible versions of the octobot image.
• Best Practices: This approach aligns with the principle of semantic versioning, where breaking changes are avoided within the same major version. It also demonstrates a good practice of automating dependency updates to enhance maintenance efficiency.

Impact Assessment

• System Impact: This change enhances the system’s ability to stay up-to-date with the latest non-breaking changes in the octobot image. It reduces the manual effort required to update the Terraform configuration for each minor version release.
• Performance & Security: By allowing the system to pull the latest compatible images, it can benefit from performance improvements and security patches more promptly.
• Maintainability: The change improves maintainability by reducing the need for frequent manual updates to the Terraform files.

Developer Notes

• Gotchas: Ensure that the 2.x version range does not introduce breaking changes. Continuous monitoring and testing are recommended to verify that new versions do not adversely affect the system.
• Edge Cases: Pay attention to the release notes of new 2.x versions to identify any potential breaking changes or required configuration adjustments.
• Future Improvements: Consider implementing automated testing and validation pipelines to further ensure that new versions integrate seamlessly with the existing system.