fix: set upper bound on datadog provider to < 4.0.0#104
Conversation
The datadog/datadog provider v4.0.0 removed the `datadog_integration_aws_lambda_arn` and `datadog_integration_aws_log_collection` resource types, breaking this component. Pin to < 4.0.0 until the component is updated to use the replacement resources. Follows up on cloudposse-terraform-components#103 which removed the AWS provider upper bound. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated the Terraform Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
8d91427
|
These changes were released in v2.1.0. |
Summary
datadog/datadogprovider to>= 3.3.0, < 4.0.0to prevent pulling v4.x which removeddatadog_integration_aws_lambda_arnanddatadog_integration_aws_log_collectionresource typesContext
The
datadog/datadogprovider v4.0.0 removed several resource types used by this component:datadog_integration_aws_lambda_arndatadog_integration_aws_log_collectionThis causes
terraform plan/applyto fail withInvalid resource typeerrors on the v2.0.0 release.Test plan
terraform initresolves datadog provider to a 3.x versionterraform planno longer errors on the removed resource types🤖 Generated with Claude Code
Summary by CodeRabbit