Open shahabhijeet opened 7 years ago
@anangaur we have multiple ApiKeys and we want to automate this process. If we have 10 ApiKeys and if they have multiple expiry dates, having this automated will help in not only knowing that the expiry date is near, but would also like to get a new key in an automated way.
Please read the following information before posting the issue.
Nuget.exe (4.1.0) dotnet.exe (1.0.4) VS 15.1.26403.7 OS (win10 v1703 (15063.483)
1) Currently with nuget.exe, you are not able to make publishing nuget package and symbol package as an atomic operation For any reason if symbol package publishing fails, there is no way to roll back nuget package publish. Feature Requests: Should have an ability to publish both packages publishing be atomic (if any symbols package fails it should not publish nuget package) and return error if any of the packages fail to publish.
2) Have an ability to query if a particular package version is already available on nuget.org? Currently the only way to find out if a particular version of package is already available on nuget.org is to actually try to publish and catch the exception.
3) Add an ability to publish symbols to local file share (this seems like a bug and not feature request) Currently when trying to publish it to local file share, it returns 0 exit code with a message that the package has been pushed successfully, but it actually does not push it to local file share. -ValidityInDays
Should return number of days the apiKey is valid
nuget.exe push <path to packageName.symbols.nupkg> -source <local publish file path> -symbolSource <local publish file path>
4) Have an ability to get number of days left for an API key validity e.g. `` Nuget.exe ApiKeyNuget.exe ApiKey -ExirationDate
Should return the date when the ApiKey expires.
``
5)
Enable PowerShell cmdlets for all operations of nuget.exe
6) Ability to Cancel Restore process once started from msbuild repo: msbuild build.proj /t:Build Which kicks off restore process Ctrl+C to cancel build process Does not cancel restore process, msbuild.exe keeps yielding saying "waiting for restore to complete"