christopher-buss / christopher-buss/bedrock

ocale: asset-permissions client

Open
#232 0 comments 0 reactions 0 assignees View on GitHub
enhancement pkg:ocale
Dominant language
TypeScript
Stars
14
Forks
0
Avg merge
7h 48m
Merged PRs (30d)
47

Description

## Description

Tracking issue. Open Cloud exposes asset-permissions, letting an asset's *who-can-use-this* state be managed declaratively. Useful when an experience depends on private assets owned by a group or another user; declaring the permission grants in config keeps drift detectable.

## Endpoints

- `/asset-permissions-api/v1/assets/permissions`

Contributor guide

Open the contributing guide

Research direction

Start by locating the existing Open Cloud client entry points and how they model other API resources. Focus on the `/asset-permissions-api/v1/assets/permissions` endpoint and determine the request and response shapes needed for declarative permissions. Done means the asset-permissions client is exposed consistently with the other clients and its behavior is covered by the repository's existing checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.