This PR bundles the Python module certifi with the API. The reason for doing this is so that the API ships with the latest certs at the time, and uses them by default. This should hopefully remove the issue where clients are using old Python interpreters that are bundled with out of date certs.
I haven't updated/created a software credits and requirements file for this change, as we are going to be adding one anyway as part of a separate ticket, so I felt it was better to leave that for now.
This PR bundles the Python module certifi with the API. The reason for doing this is so that the API ships with the latest certs at the time, and uses them by default. This should hopefully remove the issue where clients are using old Python interpreters that are bundled with out of date certs.
I haven't updated/created a software credits and requirements file for this change, as we are going to be adding one anyway as part of a separate ticket, so I felt it was better to leave that for now.