Update GitHub workflows with latest actions.

Change Summary

This update involves changes to two GitHub Actions workflows: deploy.yml and plan.yml. The modifications primarily focus on updating the versions of several GitHub Actions used within these workflows.

Technical Details

• Files Modified:
  • .github/workflows/deploy.yml
  • .github/workflows/plan.yml
• Specific Changes:
  • Updated gruntwork-io/terragrunt-action from an unspecified version to commit 95fc057922e3c3d4cc021a81a213f088f333ddef (v3).
  • Updated aws-actions/configure-aws-credentials from version v5.1.1 to commit 61815dcd50bd041e203e49132bacad1fd04d2708 (v5.1.1).
  • Updated tailscale/github-action from version v4 to commit 53acf823325fe9ca47f4cdaa951f90b4b0de5bb9 (v4).
• Commands Affected:
  • hcl fmt --check --diff for terragrunt HCL checking.
  • run --all --non-interactive -- apply and run --all --non-interactive --summary-per-unit -- plan for Terragrunt operations.

Key Learnings & Insights

• Reasoning Behind Changes:
  • The updates aim to ensure that the workflows use the latest versions of the GitHub Actions, potentially benefiting from bug fixes, performance improvements, and new features.
• Problem-Solving Approaches:
  • Identifying the need for updates through dependency management practices and keeping workflows up-to-date with the latest action versions.
• Best Practices:
  • Regularly updating dependencies to maintain security and performance standards.
  • Using specific commits instead of tags to ensure precise version control.

Impact Assessment

• System Effects:
  • These changes should enhance the reliability and security of the CI/CD pipelines by leveraging the latest versions of the GitHub Actions.
• Performance & Security:
  • Potential performance improvements and security patches from the updated actions.
• Breaking Changes:
  • No breaking changes are expected, but it is essential to monitor the workflows for any unexpected behavior post-update.

Developer Notes

• Gotchas & Edge Cases:
  • Ensure that the new versions of the actions are compatible with the existing configuration and do not introduce breaking changes.
• Future Considerations:
  • Continue to monitor dependency updates and incorporate them regularly to maintain pipeline efficiency and security.
  • Consider automating the dependency update process to reduce manual effort and potential human error.