[Pulp-dev] How to enable HTTPS for our tests in pulpcore and all plugins?
daviddavis at redhat.com
Tue Apr 27 12:25:14 UTC 2021
This is great. Thank you for working on it.
As a next step, would it make sense to create a branch and then try to
deploy a new temporary tag from that branch? Then maybe we can test a
plugin (eg pulp_npm) against this new image and see what breaks.
On Mon, Apr 26, 2021 at 5:01 PM Fabricio Aguiar <faguiard at redhat.com> wrote:
> I started this POC: https://github.com/pulp/pulp-oci-images/pull/73
> It enables https on the single container, once merged, the CI for every
> plugin will run the functional tests using https.
> Probably it would break the majority of the CIs, we need to discuss when
> is the best moment to merge this PR or discuss alternatives
> Best regards,
> Fabricio Aguiar
> Software Engineer, Pulp Project
> Red Hat Brazil - Latam <https://www.redhat.com/>
> +55 22 999000595
> On Tue, Feb 9, 2021 at 10:55 AM Fabricio Aguiar <faguiard at redhat.com>
>> Our nginx conf only supports http now:
>> For not breaking all plugins, I believe we can build a new CI image that
>> supports https.
>> Maybe a template_config parameter - test_https: true would switch the
>> Best regards,
>> Fabricio Aguiar
>> Software Engineer, Pulp Project
>> Red Hat Brazil - Latam <https://www.redhat.com/>
>> +55 22 999000595
>> On Tue, Feb 9, 2021 at 5:16 AM Matthias Dellweg <mdellweg at redhat.com>
>>> I believe this is at least solving the problem partially:
>>> On Mon, Feb 8, 2021 at 9:48 PM Brian Bouterse <bmbouter at redhat.com>
>>>> I believe all of our plugins (and CI) require HTTP and do not work with
>>>> HTTPS. I'm not well versed in what needs to be done to fix this, but I
>>>> think we should fix it.
>>>> Can the CI group have a 30 min call to talk over what needs to be done?
>>>> Or maybe share some info here?
>>>> The main issue I'm aware of is that the tests are not prepared to trust
>>>> an https certificate that is self-signed. I'm not exactly sure where we can
>>>> change that in one place either.
>>>> Pulp-dev mailing list
>>>> Pulp-dev at redhat.com
>>> Pulp-dev mailing list
>>> Pulp-dev at redhat.com
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev