How I overcame SSL handshake issues about puppet-chocolatey

[ferventcoder]

@vandelin586 For the install of Chocolatey itself, we're adding newer TLS versions automatically when supported by your environment - puppetlabs@4e31ed7

[ferventcoder]

@vandelin586 I'd like to clear up a possible misconception here.

Thing was that it was not working, after some research I found that by default chocolatey reaches out to the vendor website, downloads chocolatey package, and then install it ..

I think you are saying that a package on the community repository (https://chocolatey.org/packages) is downloaded by Chocolatey, and the package scripts from that community package will reach out to download software from the vendor website and install it. This is due to redistribution rights and copyright law (for the software that the package represents) in many instances since the site is public.

It does require an understanding that Chocolatey != Chocolatey.org packages. Chocolatey is completely decentralized as you have noted in saying you download the Chocolatey nupkg and host it on your own internal repository.

Typically organizations using Chocolatey will come to the community repository for two reasons, to grab a version or the latest version of the Chocolatey nupkg and put it on their internal server, and the second time is when they want to use an existing package on the community site but without the hit to the internet. So they do a process called internalization - https://chocolatey.org/docs/how-to-recompile-packages. Chocolatey for Business has Package Internalizer, which will do the internalization for you automatically.

[vandelin586]

Thank you for the clarification and for the updates on "adding newer TLS versions automatically"

I look forward to the new updates and I will look into chocolatey for business and discuss with the team those options as well.