Skip to content

fix: terraform init waiting on user response#46

Merged
sprajeesh merged 2 commits into
mainfrom
fix/terraform-backend-config
Jul 9, 2026
Merged

fix: terraform init waiting on user response#46
sprajeesh merged 2 commits into
mainfrom
fix/terraform-backend-config

Conversation

@sprajeesh

Copy link
Copy Markdown
Owner

Piped a yes to the terraform init command...

sprajeesh and others added 2 commits July 9, 2026 17:34
…ted in 1.10.x)

The endpoints.s3 parameter is not valid for the S3 backend in Terraform 1.10.x.
Use the standard 'endpoint' parameter instead which is compatible with OCI's
S3-compatible Object Storage API.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Use 'echo "yes" | terraform init' to automatically answer the state migration
confirmation prompt in CI without requiring -input=false. The -migrate-state
flag alone still prompts interactively, so piping "yes" to stdin answers it
automatically without disabling all input prompts.

This avoids the "Can't ask approval for state migration when interactive
input is disabled" error that occurs when combining -input=false with
-migrate-state.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@sprajeesh, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d0930be3-49a9-4b95-b6c3-aa49eff31f01

📥 Commits

Reviewing files that changed from the base of the PR and between 40efcbd and f8da199.

📒 Files selected for processing (2)
  • .github/workflows/push.yml
  • infra/oci/backend.tf
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/terraform-backend-config

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sprajeesh sprajeesh merged commit 10f3ff4 into main Jul 9, 2026
5 checks passed
@sprajeesh sprajeesh deleted the fix/terraform-backend-config branch July 9, 2026 05:41
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.

1 participant