refactor(elasticsearch): replace no-op loop-over-group in upgrade includes with a membership guard - #189
Conversation
|
Warning Review limit reached
Next review available in: 59 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Path: .coderabbit.yaml Review profile: CHILL 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 |
1ce506f to
c7c9bc6
Compare
…ludes with a membership guard
c7c9bc6 to
dd9d55b
Compare
Both rolling-upgrade includes in
main.ymllooped over the whole elasticsearch group withhostvars[item].inventory_hostname == inventory_hostname, which only ever matches the host itself: the loop ran the include at most once and produced one skip line per other group member per host (98 skip lines on a 7-node cluster), suggesting per-group behaviour that doesn't exist.The loop did double as an accidental group-membership check (a loop over an empty/absent group skips the task), so the replacement keeps that explicitly:
inventory_hostname in groups[...] | default([]). Thedefault([])also removes an undefined-variable failure when the group is absent, which the old construct would have hit.Covered in
tests/integration/elasticsearch_upgrade_detection_contract.yml; fails if either the loop returns or the membership guard is dropped.