Pull Request Check List

Resolves: #1556

• Added tests for changed code.
• Updated documentation for changed code.

Here is a proposition to disable SSL verification that makes poetry easier to use in corporate environments.

So unfortunately I started from master because the contributing guide https://python-poetry.org/docs/contributing/#how-to-contribute does not mention to start from develop.

I tried to reproduce the contrib on top of develop this morning but I must admit I gave up after noticing that poetry now depends on poetry-core having its own repository. I guess it would not be hard to add what's needed in poetry-core, but since I don't know the codebase it takes me time walking in the debugger to understand what's going on. The exception I had from poetry-core was related to the trusted field I've added that is not recognized, so modifying poetry-schema.json in poetry is not enough anymore, something must be done in the code and I didn't invastigated much. The commit I made on top of develop is available on top of this other branch: https://github.com/Celeborn2BeAlive/poetry/commits/option-to-disable-ssl-verify-develop

About tests I had no clear idea how to test this feature automatically. I did manual tests on one of our internal project that depends on packages from a private and repository and it did work.

Finally I modified the documentation but had issues building it: the resulting website does not contain valid html and is basically just a subpart of the html of the official documentation. Is there another step to build the full website ?