OSAC-1733: Manage osac-aap's lock_branch in Terraform - #151
Conversation
osac-aap was locked read-only via a one-off gh api call after being merged into osac (OSAC-1732/OSAC-1733), the same way fulfillment-service and osac-operator originally were before PR osac-project#150 fixed it for them. Extends that same fix to osac-aap so its lock survives the next Terraform auto-apply cycle instead of silently reverting.
|
Warning Review limit reached
Next review available in: 41 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Repository: osac-project/coderabbit/.coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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 |
Summary
osac-aap was locked read-only via a one-off
gh apicall after being merged intoosac(OSAC-1732/OSAC-1733) -- the same wayfulfillment-serviceandosac-operatororiginally were, before #150 fixed it for them by declaringlock_branchin Terraform (this repo'sgithub_branch_protectionis a full-replace resource, so an out-of-band API toggle silently reverts on the next auto-apply cycle).This extends that same fix to
osac-aap, using thelock_branchvariable #150 already added tomodules/common_repository.Test plan
terraform planin CI should show onlylock_branch: false -> trueformodule.repo_cloudkit_aap, no other diff