-
Notifications
You must be signed in to change notification settings - Fork 905
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
Packages.config should include all options (including ignorechecksums) #886
Comments
On a side note, running |
I guess I wouldn't have thought of this as an enhancement, but maybe the problem is that https://github.com/chocolatey/choco/wiki/CommandsInstall#packagesconfig doesn't call out which options work in a .config file and which ones don't - without some clarity there it seems like a sensible assumption that all of the options listed in the following section should be expected to work as advertised. Obviously, though, you need to manage your workload as you see fit. Thanks for the swift attention. |
@cori As I mentioned over in the disqus notes, I think this should include all options that can be passed. |
@cori I could go either way. Unexpected behavior could make it a bug, but as we did not add that functionality yet I think of it as an enhancement. Forgotten functionality could make it a bug. Like I said, I could go either way. 👍 |
don't see a note on the disqus thread, but probably more important to get it here! |
yes, more important to get it here. Perhaps it wasn't on disqus. Where did we talk about this already? |
Found it - you replied to a stackoverflow comment: http://stackoverflow.com/questions/34106680/how-to-use-custom-parameters-in-chocolatey-config-file/34111537?noredirect=1#comment64776855_34111537 |
Would be nice to include options that come in from business editions as well here. |
@gep13 added an issue here: chocolatey/chocolatey-licensed-issues#317 |
A mistake was made in previous commit, where property name was changed to use a more consistent version, however, the wrong property name was changed, and this wasn't tested before pushing up the commit.
When using a packages.config file, output the evaluated package configuration to the debug stream so that it is available for troubleshooting (and our Pester tests). Also update the checksum type logic to store in the right property.
Add Pester tests to test the options passed via a packages.config file.
Update the packages.config to be easier to read in the Pester tests. Update the configurations to use specific strings instead of all of them being the same "string". This will allow us to identify that they are actually what they're supposed to be.
When using a packages.config file, output the evaluated package configuration to the debug stream so that it is available for troubleshooting (and our Pester tests). Also update the checksum type logic to store in the right property.
Add Pester tests to test the options passed via a packages.config file.
Update the packages.config to be easier to read in the Pester tests. Update the configurations to use specific strings instead of all of them being the same "string". This will allow us to identify that they are actually what they're supposed to be.
Update the debug logging when a packages.config file is being used to output the start and end of the configuration on independent lines. This allows us to update the test to get these start and end points and not play guessing games with how long we think the output should be. Updating this test allows Chocolatey Licensed Extension to be included and the tests still pass.
Update the debug logging when a packages.config file is being used to output the start and end of the configuration on independent lines. This allows us to update the test to get these start and end points and not play guessing games with how long we think the output should be. Updating this test allows Chocolatey Licensed Extension to be included and the tests still pass.
Update the debug logging when a packages.config file is being used to output the start and end of the configuration on independent lines. This allows us to update the test to get these start and end points and not play guessing games with how long we think the output should be. Updating this test allows Chocolatey Licensed Extension to be included and the tests still pass.
Update the debug logging when a packages.config file is being used to output the start and end of the configuration on independent lines. This allows us to update the test to get these start and end points and not play guessing games with how long we think the output should be. Updating this test allows Chocolatey Licensed Extension to be included and the tests still pass.
(#886, 2693) Update packages.config install logging and add back resolve or load method for Assembly Resolution
@AdmiringWorm this still needs documentation. See chocolatey/docs#403 |
* release/1.2.0: (374 commits) (maint) Add incoming arguments available in Licensed Extension (chocolatey#798) Add missing pin option in tab completion (chocolatey#2860) Add e2e tests for new PS cmdlet (maint) Fix Chocolatey path in docs generation (chocolatey#2860) Add new PS helper to get maintainer specific paths (chocolatey#2816) Update to latest Chocolatey NuGet.Core (chocolatey#2693) Re-add old resolve or load method (chocolatey#886) Update packages.config install logging (chocolatey#1185) Always pass in hook scripts event if empty Update tests/chocolatey-tests/commands/choco-outdated.Tests.ps1 (chocolatey#2801) Pin Chocolatey packages for outdated tests (chocolatey#886) Use specific strings for configurations (chocolatey#886) Add Pester tests for packages.config (chocolatey#886) Debug log Package configuration (chocolatey#1185) Be explicit with expected exit codes (maint) Pester test directory structure shuffle (chocolatey#1185) Add tests for hook scripts (maint) Minor formatting change (chocolatey#798) Add tests for pinning package on install (chocolatey#2787) Restore Chocolatey snapshot before sxs ...
🎉 This issue has been resolved in version 1.2.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
* master: (maint) Add incoming arguments available in Licensed Extension (#798) Add missing pin option in tab completion (#2860) Add e2e tests for new PS cmdlet (maint) Fix Chocolatey path in docs generation (#2860) Add new PS helper to get maintainer specific paths (#2816) Update to latest Chocolatey NuGet.Core (#2693) Re-add old resolve or load method (#886) Update packages.config install logging
What You Are Seeing?
cinst on command-line using a .config file disregards ignorechecksum for specific packages.
What is Expected?
an entry in a .config file that includes `ignorechecksums="true" or another of the aliases from https://github.com/chocolatey/choco/wiki/CommandsInstall#options-and-switches should honor the ignorechecksums directive and allow, for that specific package,an installer that fails the checksums verification to be installed.
How Did You Get This To Happen? (Steps to Reproduce)
ran
cinst rt.config -y
using the attached rt.config.txt file.rt.config.txt
Output Log
chocolatey.log: https://gist.github.com/cori/01ff60e1638b75f38a25cbe41e7a0a16
choco.summary.log: https://gist.github.com/cori/b51791c5e22e19180d1e31e0eee717f1
The text was updated successfully, but these errors were encountered: