Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

temp: pin cloudflare provider version to 4 #57

Closed

Conversation

DesmondH0
Copy link

Details

  • A new cloudflare provider version had released around 14h ago which contains brunch of breaking changes
  • We would need to pin the version to 4.X for keeping the module working before its ready to upgrade

Ref

@DesmondH0 DesmondH0 requested review from a team as code owners January 29, 2025 15:47
@mergify mergify bot added the triage Needs triage label Jan 29, 2025
@RoseSecurity
Copy link

Thank you for raising this.

It's a tricky issue to navigate when it comes to breaking changes with providers, modules, and components. To maintain stability while waiting for module updates, Cloud Posse decided that the best course of action is to pin providers to major and minor versions in downstream components (e.g., ~> 4.0). This approach ensures compatibility while allowing patch updates without the rigidity of exact version pinning or the complexity of managing the .terraform.lock.hcl. Pinning in upstream modules was considered but would create compatibility issues when newer major versions are released.

@DesmondH0
Copy link
Author

Thank you for raising this.

It's a tricky issue to navigate when it comes to breaking changes with providers, modules, and components. To maintain stability while waiting for module updates, Cloud Posse decided that the best course of action is to pin providers to major and minor versions in downstream components (e.g., ~> 4.0). This approach ensures compatibility while allowing patch updates without the rigidity of exact version pinning or the complexity of managing the .terraform.lock.hcl. Pinning in upstream modules was considered but would create compatibility issues when newer major versions are released.

Thanks, updated PR to pin latest minor version as well.

@RoseSecurity
Copy link

Sorry for the confusion. To clarify, Cloud Posse's general practice is to avoid pinning provider versions in upstream modules to ensure broader compatibility for the community. Instead, provider versions are pinned at the component level to major and minor versions (e.g., ~> 4.0) to maintain stability while allowing patch updates. You can find more details on this approach in this doc. For now, I am going to close this PR

@mergify mergify bot removed the triage Needs triage label Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants