A way to remove sources without knowing their names

[ghost]

It would be nice if there was a direct way to remove sources we don't know the name of (something like, choco source remove all).

Example use case: You need to use a script to move a machine from one environment to the other, and you need to disable package sources associated with the old environment, without your script necessarily knowing what the original environment was. Simply removing all configured sources before adding the new ones is the ideal way to go.

[ferventcoder]

@joshuathornton862 thanks for adding that. I wanted to link where the original conversation took place, was that on gitter?

[ghost]

Sure! It was in #packaging on Slack on 2/12 and 2/13.

…

On Tue, Feb 20, 2018 at 10:29 AM, Rob Reynolds ***@***.***> wrote: @joshuathornton862 <https://github.com/joshuathornton862> thanks for adding that. I wanted to link where the original conversation took place, was that on gitter? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1493 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Aiwqt3WhXw_h7ocUsn1S7ipPOuq0UShnks5tWvLngaJpZM4SD6iF> .

[ferventcoder]

Conversation was at https://powershell.slack.com/archives/C03P5GVMR/p1518474729000123

[renehernandez]

@ferventcoder I want to give a try to implement this. I am a new contributor to this repo. Any suggestions?

[gep13]

@renehernandez if I may make a suggestion...

On my stream I have recently been working on adding a new Export Command for Chocolatey, which walks through the process of getting started with the Chocolatey code base. This started on this stream here:

https://github.com/gep13-oss/live-streams/blob/master/README.md

And continued here:

https://github.com/gep13-oss/live-streams/blob/master/README.md

And in this stream, @ferventcoder and I went through a PR review of what was created:

https://github.com/gep13-oss/live-streams/blob/master/README.md

These could be a good place to get started.

Let me know if you have any questions.

[renehernandez]

I have already drafted the implementation for this. What is preferred for this feature:

• choco source remove all or
• choco source remove -n=all

[renehernandez]

@gep13 Also, I couldn't find a good example of how to test source removal in the solution. Any suggestions there?

[renehernandez]

@ferventcoder @gep13 Any suggestions to my previous comments?

[magnani1]

Put in .bat or .cmd:

SET "choco=%systemdrive%\ProgramData\chocolatey\choco.exe"
for /f "tokens=1" %%i in ('%choco% source list') do %choco% source remove -name %%i

[magnani1]

It would be nice if there was a direct way to remove sources we don't know the name of (something like, choco source remove all).

Example use case: You need to use a script to move a machine from one environment to the other, and you need to disable package sources associated with the old environment, without your script necessarily knowing what the original environment was. Simply removing all configured sources before adding the new ones is the ideal way to go.

Put in .bat or .cmd:

SET "choco=%systemdrive%\ProgramData\chocolatey\choco.exe"
for /f "tokens=1" %%i in ('%choco% source list') do %choco% source remove -name %%i

[ferventcoder]

this feel more appropriate - choco source remove all

[vexx32]

@corbob do you think this would be a good kind of test to include in the Pester tests you're currently working on, or would it be better to include in the C# unit tests for the source command?