feat(badges): augment validateBadge payload for attendee-networking connect resolve#571
feat(badges): augment validateBadge payload for attendee-networking connect resolve#571smarcet wants to merge 1 commit into
Conversation
…onnect resolve
Extend GET /summits/{id}/badge/{badge}/validate so attendee-networking-api can
resolve a scanned badge to a connection identity (SDS D26 / ftn-docsnsklz #40):
- add ticket.owner.id (keys the member-less pre-account request, D27)
- expand the nested ticket.owner.member {id, first_name, last_name, pic}
(member.id is the D15 identity; member is absent for member-less attendees)
No auth change is needed: the auth.user middleware passes service tokens
through (required-groups gate only user tokens), so a client-credentials
service account holding the read scope already reaches the route.
Tests (OAuth2SummitApiTest): the member case asserts the expanded member
object; the member-less case (D27) asserts the member object is absent while
attendee id + email are present. InsertSummitTestData gains a member-less
attendee with a badge to cover it.
|
📘 OpenAPI / Swagger preview ➡️ https://OpenStackweb.github.io/summit-api/openapi/pr-571/ This page is automatically updated on each push to this PR. |
|
Warning Review limit reached
Next review available in: 52 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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 |
smarcet
force-pushed
the
feat/augment-validate-badge
branch
from
7c93012 to
8af8b08
Compare
|
📘 OpenAPI / Swagger preview ➡️ https://OpenStackweb.github.io/summit-api/openapi/pr-571/ This page is automatically updated on each push to this PR. |
1 participant
https://app.clickup.com/t/9014802374/86bauc5hf
Extend GET /summits/{id}/badge/{badge}/validate so attendee-networking-api can resolve a scanned badge to a connection identity (SDS D26 / ftn-docsnsklz #40):
No auth change is needed: the auth.user middleware passes service tokens through (required-groups gate only user tokens), so a client-credentials service account holding the read scope already reaches the route.
Tests (OAuth2SummitApiTest): the member case asserts the expanded member object; the member-less case (D27) asserts the member object is absent while attendee id + email are present. InsertSummitTestData gains a member-less attendee with a badge to cover it.