iterative / iterative/gto

Permission control

Open
#86 0 comments 0 reactions 0 assignees View on GitHub
enhancement studio
Dominant language
Python
Stars
162
Forks
18
PR merge metrics
No merged PRs in 30d

Description

@dberenbaum feedback

> How can I have permissions/control over who can register/promote to different environments?

Need to think about the way. We need to reuse GH permissions, as I guess we can't setup another layer of security around this. The question is, what scenarios does it solve and how implementations will look like.

Another question is how it will be blended with Studio permissions/RBAC in future, if we'll decide to make some. As Model Registry is a central part of some workflows, we'll need to come up with about something here.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.