|
crobinson opened 1 month ago
|
||||
|
Not quite understand the situation. Can you please elaborate? |
||||
|
|
Yes, Specific users should only have access, based on the roll to specific docker packages. ex: User1 can only access package app:1.0.0 User2 can access 1.0.0 and 2.0.0 |
||||
|
|
This will be very complex. I'd suggest to publish different package versions to different projects so that you can use project specific access control. |
||||
|
|
Want to mention that you may also publish same package version to multiple projects for access control purpose if desired. They will share same blob storage without extra disk space. |
||||
|
|
Robin Shen changed state to 'Closed' 1 month ago
|
| Type |
Improvement
|
| Priority |
Minor
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Watchers (3)
Since packages were introduced, we started using OneDev for our package management and used the API to create Guest Users with a specific group, and a specific role to only allow viewing of packages.
However, for each customer, we have a user that pulls updated packages when we release them. I would like the ability to limit by package version ex: 2.3.x or <=2.3