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

dotnet nuget push does not recognize --configfile option #14088

Open
miitors-tbm opened this issue Feb 6, 2025 · 0 comments
Open

dotnet nuget push does not recognize --configfile option #14088

miitors-tbm opened this issue Feb 6, 2025 · 0 comments

Comments

@miitors-tbm
Copy link

miitors-tbm commented Feb 6, 2025

NuGet Product Used

dotnet.exe

Product Version

8.0.405

Worked before?

No

Impact

I'm unable to use this version

Repro Steps & Context

To reproduce, run a push command like dotnet nuget push MyPackage.1.0.0.nupkg -k [...] -s [...] --configfile path/to/nuget.config.

Expected outcome

The package is pushed to the specified source using the specified config file.

Actual outcome

An error: Unrecognized option '--configfile' error is returned.

Other details

My particular reason for needing this is that the source I want to push to is using HTTP authentication, and the credentials are stored in a NuGet config file.

Running an equivalent command using nuget.exe such as ./nuget.exe push MyPackage.1.0.0.nupkg [...] -Source [...] -ConfigFile path/to/nuget.config works as expected.

Verbose Logs

Specify --help for a list of available options and commands.
error: Unrecognized option '--configfile'


Usage: dotnet nuget push [arguments] [options]

Arguments:
  [root]  Specify the path to the package and your API key to push the package to the server.

Options:
  -h|--help                      Show help information
  --force-english-output         Forces the application to run using an invariant, English-based culture.
  -s|--source <source>           Package source (URL, UNC/folder path or package source name) to use. Defaults to DefaultPushSource if specified in NuGet.Config.
  -ss|--symbol-source <source>   Symbol server URL to use.
  -t|--timeout <timeout>         Timeout for pushing to a server in seconds. Defaults to 300 seconds (5 minutes).
  -k|--api-key <apiKey>          The API key for the server.
  -sk|--symbol-api-key <apiKey>  The API key for the symbol server.
  -d|--disable-buffering         Disable buffering when pushing to an HTTP(S) server to decrease memory usage.
  -n|--no-symbols                If a symbols package exists, it will not be pushed to a symbols server.
  --no-service-endpoint          Does not append "api/v2/package" to the source URL.
  --interactive                  Allow the command to block and require manual action for operations like authentication.
  --skip-duplicate               If a package and version already exists, skip it and continue with the next package in the push, if any.

Full dotnet --info output

.NET SDK:
 Version:           8.0.405
 Commit:            fb1830d421
 Workload version:  8.0.400-manifests.a85f4036
 MSBuild version:   17.11.9+a69bbaaf5

Runtime Environment:
 OS Name:     debian
 OS Version:  12
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /usr/share/dotnet/sdk/8.0.405/

.NET workloads installed:
Configured to use loose manifests when installing new manifests.
There are no installed workloads to display.

Host:
  Version:      8.0.12
  Architecture: x64
  Commit:       89ef51c5d8

.NET SDKs installed:
  8.0.405 [/usr/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.12 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.12 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants