You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 18, 2020. It is now read-only.
If a user is authenticating using a CoreUpdate administrator account when using updateservicectl, they should be able to download any packages that are on the server using updateservicectl pkg download, and not just the ones that are considered "public" by the PublicPackagesList api call (which currently are any packages associated with an application that has at least one public channel).
This particularly affects people running private versions of CoreUpdate with no public channels, or ones that only pull public channels from an upstream CoreUpdate (upstream channels are private and can't be configured otherwise). In this case, they won't have any public channels, which means that they won't be able to download any packages associated with that application.
If a user is authenticating using a CoreUpdate administrator account when using updateservicectl, they should be able to download any packages that are on the server using
updateservicectl pkg download, and not just the ones that are considered "public" by the PublicPackagesList api call (which currently are any packages associated with an application that has at least one public channel).This particularly affects people running private versions of CoreUpdate with no public channels, or ones that only pull public channels from an upstream CoreUpdate (upstream channels are private and can't be configured otherwise). In this case, they won't have any public channels, which means that they won't be able to download any packages associated with that application.