dotnet-nuget doesn't support verbosity

[livarcocc]

From @kasper3 on December 29, 2017 22:10

dotnet nuget push --source {uri} path.nupkg -v q

# error: Unrecognized option '-v'

dotnet nuget push --source {uri} path.nupkg --verbosity quiet

# error: Unrecognized option '--verbosity'

However,

dotnet nuget --verbosity quiet push --source {uri} path.nupkg

doesn't throw but doesn't quiet the verbosity either.

This breaks what --help quotes:

Common options:
  -v|--verbosity        Set the verbosity level of the command. Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic].
  -h|--help             Show help.

--verbosity is NOT a common option, only --help is

Copied from original issue: dotnet/cli#8306

[livarcocc]

It seems like we are passing down the -v q to nuget but nuget does not recognize the argument. If nuget does not recognize this argument, please, re-activate the CLI issue and we will figure out how to make it clear that not exactly all commands respect this argument.

[zhili1208]

looks like NuGet.Command.Xplat don't have verbosity option, we should add it.

[rrelyea]

should fix across the set of commands as appropriate.
dotnet add package -- likely verbosity should apply to restore under covers, and perhaps restore default verbosity should change.
dotnet nuget sources - in nuget.exe, supported a verbosity quiet.
etc...

[rrelyea]

When we do this, consider which of these tests to add back in... (look at history):
test/NuGet.Core.FuncTests/NuGet.XPlat.FuncTest/BasicLoggingTests.cs

[Sebbstar]

is there any workaround to troubleshoot (enable logs) for dotnet nuget push?