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

Allow users to validate Chocolatey sources directly #3640

Open
2 tasks done
pauby opened this issue Feb 28, 2025 · 2 comments
Open
2 tasks done

Allow users to validate Chocolatey sources directly #3640

pauby opened this issue Feb 28, 2025 · 2 comments
Labels
0 - _Triaging Feature Issues that introduce new functionality to the project, instead of updating existing functionality

Comments

@pauby
Copy link
Member

pauby commented Feb 28, 2025

(To vote for this issue, please add a 👍 emoji to the issue description)

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

In this issue comment the user would have benefitted from Chocolatey CLI being able to validate the configured sources.

Describe The Solution. Why is it needed?

Adding a command such as choco source validate (naming is hard) to allow all, or a specific source (perhaps using choco source validate --source <SOURCE>) to be "checked" to ensure Chocolatey CLI can use it.

What "checked" means we would need to define. But it could be as simple as retrieving a package list, or:

  • Check if it's reachable. Is the URL correct?
  • What type of source is it: v2 oData, v3 JSON, local folder / shared drive, etc.
  • If authentication is provided, can we authenticate?
  • Does it have a search endpoint?

Additional Context

No response

Related Issues

@pauby pauby added 0 - _Triaging Feature Issues that introduce new functionality to the project, instead of updating existing functionality labels Feb 28, 2025
@TheCakeIsNaOH
Copy link
Member

Unsure if a dup or just related to #3602

@pauby
Copy link
Member Author

pauby commented Mar 2, 2025

🤦 It is. As this one has two upvotes, to keep them I'll mark #3602 as a duplicate and bring some information from that issue over here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - _Triaging Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants