[self-hosted] Use cscli lapi status for CrowdSec readiness check in installer#5949
[self-hosted] Use cscli lapi status for CrowdSec readiness check in installer#5949
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe change modifies the CrowdSec readiness check in the getting-started.sh script, replacing the CAPI status command with an LAPI status command to verify CrowdSec availability during the Traefik initialization flow. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
|



Describe your changes
The installer's CrowdSec readiness loop gated bouncer registration on
cscli capi status, which checks Central API (CAPI) connectivity. Bouncer registration is a purely local operation against LAPI, so a CAPI 403 (e.g. rate limit, misconfiguration) would cause the installer to skip CrowdSec setup unnecessarily. Switch the wait tocscli lapi statusto match the container healthcheck.Issue ticket number and link
Related: #5944
Stack
Checklist
Documentation
Select exactly one:
Docs on main already reference
cscli lapi status(netbirdio/docs#709).Docs PR URL (required if "docs added" is checked)
Paste the PR link from https://github.com/netbirdio/docs here:
https://github.com/netbirdio/docs/pull/__
Summary by CodeRabbit