test: add consumer credential ginkgo e2e#27
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ 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: Organization UI 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 new Ginkgo-based E2E coverage for the consumer and credential CLI commands, validating CRUD behavior and key validation paths against a real APISIX Admin API while keeping existing mock/unit tests unchanged.
Changes:
- Added Ordered Ginkgo E2E specs for
consumercreate/list/export/get/update/delete flows (including required-flag and not-found behavior). - Added Ordered Ginkgo E2E specs for
credentialcreate/list/get/update/delete flows plus validation coverage (missing flags / missing credentialid).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
Verification
Note: full local E2E currently depends on the array-nodes compatibility fix in #26 when the local APISIX contains routes whose upstream.nodes is returned as an array.