Automatic migration of NuGet.config credentials doesn't work
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Automatic migration of NuGet.config credentials doesn't work. I've tried with credentials stored in the Nuget.config file both encrypted and in plaintext.
Repro steps
- Have an authenticated source setup in your nuget.config e.g. Artifactory
- Run paket.exe convert-from-nuget
Expected behavior
The current credentials in the NuGet.config are migrated to the paket.dependencies file.
Actual behavior
No credentials are added and when the paket install is run authentication fails.
Known workarounds
Run the conversion and then manually update the paket.dependencies file adding the credentials
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the paket.exe convert-from-nuget entry point and trace how authenticated sources from nuget.config are handled when generating paket.dependencies. Verify the encrypted and plaintext credential cases from the reproduction steps, and confirm that paket install authenticates successfully after conversion.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100