lablup / lablup/backend.ai

Carry the resolved field set into the spec layer

Open
#14,129 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
670
Forks
183
Avg merge
17h 7m
Merged PRs (30d)
358

Description

Foundation implementation of the enforcement BEP: the permission check resolves the effective field set (role field_permissions intersected with the grant cap's field list, per operation) and the processor carries it into the action pipeline in the interface shape the BEP fixes, so queriers, searchers, updaters and lookups receive it uniformly. Includes the GraphQL rejection point for explicitly requested unpermitted fields, and one representative entity wired end-to-end as the reference. The sweep across the remaining entities is the team-distributed follow-up (BA-7562).

JIRA Issue: BA-7598

Contributor guide

Open the contributing guide

Research direction

Start at the permission check that resolves the effective field set, then trace how the processor carries it through the action pipeline. Inspect the GraphQL rejection point and the representative entity wired end-to-end. Done means the resolved set reaches queriers, searchers, updaters, and lookups uniformly, and explicitly requested unpermitted fields are rejected; the remaining-entity sweep is BA-7562.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, python
Domain
api, authorization
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.