Oslo.config deprecated parameter enforce_type and change its
default value to True in Ifa552de0a994e40388cbc9f7dbaa55700ca276b0.
Remove the usage of it to avoid DeprecationWarning: "Using the
'enforce_type' argument is deprecated in version '4.0' and will be
removed in version '5.0': The argument enforce_type has changed its
default value to True and then will be removed completely."
Related--Bug: #1517839
Change-Id: If045d76574823f29c58b39a104354abc1407cb8d
There is now a new configuration option "barbican_auth" in the
certificates section, to specify which auth plugin to use when
communicating with Barbican. This is because the default option (using
ACLs inside Barbican to control access) should be ok as a default
workflow, but it might be required to use other methods depending on
your deployment. For example, another possible auth method would be
BarbicanTrustAuth, utilizing Keystone Trusts.
While we're in this file, prune the unused (and really bad) method that
would *actually* delete certs from Barbican (not in our scope).
This is (nearly) a direct port of the work done in:
https://review.openstack.org/#/c/216140/
Change-Id: Id8386c36c7acfd954bc2309947345dfe31124b16
Currently local_cert_manager is never enabled if 'cert_manager_class'
is set to 'neutron_lbaas.common.cert_manager.local_cert_manager'.
Because due to initialization order of config parameters.
This fixes it to correct order.
Change-Id: I0b60e9034e113160ec8347da52d67c4835c90cbf
Adam Harwell