fix: add Terraform provider monitoring to Dependabot#7
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 16 minutes and 49 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
There was a problem hiding this comment.
Pull request overview
Adds a Dependabot entry intended to monitor Terraform provider versions alongside the existing GitHub Actions dependency checks.
Changes:
- Extend
.github/dependabot.ymlwith a newpackage-ecosystem: "terraform"update rule. - Configure the Terraform updates to run on a weekly schedule.
| # Terraform providers | ||
| - package-ecosystem: "terraform" | ||
| directory: "/" | ||
| schedule: | ||
| interval: "weekly" |
There was a problem hiding this comment.
The repo currently doesn’t contain any committed Terraform configuration files (*.tf / *.tf.json), so Dependabot’s terraform updater won’t find dependency files in directory: "/" (it only scans real Terraform files, not HCL snippets embedded in Markdown). This means the new entry likely won’t achieve the stated goal and may show Dependabot “no dependency files found” errors.
Consider either (a) removing this entry until Terraform code is added to the repo, or (b) pointing directory to the actual path where Terraform files are checked in (and adding open-pull-requests-limit if you want parity with the existing GitHub Actions entry).
Summary
Test plan