86c5bc2b45
We currently only have letsencrypt_test_only as a single flag that sets tests to use the letsencrypt staging environment and also generates a self-signed certificate. However, for initial testing we actually want to fully generate certificates on hosts, but using the staging environment (i.e. *not* generate self-signed certs). Thus we need to split this option into two, so the gate tests still use staging+self-signed, but in-progress production hosts can just using the staging flag. These variables are split, and graphite01.opendev.org is made to create staging certificates. Also remove some debugging that is no longer necessary. Change-Id: I08959ba904f821c9408d8f363542502cd76a30a4
7 lines
329 B
Django/Jinja
7 lines
329 B
Django/Jinja
# We don't want CI tests trying to really authenticate against
|
|
# letsencrypt; apart from just being unfriendly it might cause quota
|
|
# issues. As we don't have the authentication keys exposed in the
|
|
# gate, only generate a place-holder self-signed cert for testing.
|
|
letsencrypt_use_staging: True
|
|
letsencrypt_self_sign_only: True
|