Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NuGet package permissions for shared packages across projects #1894

Closed
tothegills opened this issue Aug 13, 2015 · 5 comments
Closed

NuGet package permissions for shared packages across projects #1894

tothegills opened this issue Aug 13, 2015 · 5 comments
Assignees
Labels
Milestone

Comments

@tothegills
Copy link

@tothegills tothegills commented Aug 13, 2015

Assign Package 1 to Project 1
Give user permissions to Project 1
Assign Package 1 to Project 2
DO NOT give user permissions to Project 2
The user can not download Package 1 anymore

See http://help.octopusdeploy.com/discussions/questions/5309

@tothegills tothegills added the kind/bug label Aug 13, 2015
@tothegills

This comment has been minimized.

Copy link
Author

@tothegills tothegills commented Aug 14, 2015

Also applies to uploading/pushing packages

@tothegills tothegills changed the title NuGet package download permissions NuGet package permissions Aug 14, 2015
@yooakim

This comment has been minimized.

Copy link

@yooakim yooakim commented Aug 15, 2015

Thanks @scubamandan for pointing to this when I commented on #758 - I think they are related.

We had a similar issue when uploading packages to the built-in NuGet repository.

A team had access to a specific project and associated package. When the project was cloned the user could no longer upload packages.

@vanessalove vanessalove changed the title NuGet package permissions NuGet package permissions for shared packages across projects Aug 26, 2015
@DamianMac DamianMac added ready and removed ready labels Aug 26, 2015
@vanessalove

This comment has been minimized.

Copy link
Contributor

@vanessalove vanessalove commented Aug 26, 2015

The pushing package logic is correct - you should have permissions for both projects to push the package - you need to be aware if it is going to trigger an automatic release or not etc.

Downloading is a bug and should be available.

@DamianMac DamianMac added the ready label Nov 13, 2015
@tothegills tothegills added in progress and removed ready labels Nov 19, 2015
@tothegills tothegills self-assigned this Nov 19, 2015
@tothegills tothegills closed this Nov 24, 2015
@tothegills tothegills removed the in progress label Nov 24, 2015
@octoreleasebot

This comment has been minimized.

Copy link

@octoreleasebot octoreleasebot commented Nov 24, 2015

Release Note: Downloading packages from built-in NuGet repository only requires permissions to one project that uses the package

@lock

This comment has been minimized.

Copy link

@lock lock bot commented Nov 26, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
5 participants
You can’t perform that action at this time.