06b76aa6e8
Currently etc/barbican/barbican.conf is maintained by hand and can not be regenerated based on the config settings defined in the code. A common pattern for OpenStack projects is to use oslo-config-generator for that task. Co-Authored-By: Randall Burt <randall.burt@rackspace.com> Depends-On: I90870dcb49cd96f6bf0fe353fa6e779ffd87a5af Closes-Bug: #1584789 Change-Id: I5f3dcd2fc982f1178ef7dd662c24d3166f91b266
22 lines
738 B
Plaintext
22 lines
738 B
Plaintext
[DEFAULT]
|
|
output_file = etc/barbican/barbican.conf.sample
|
|
namespace = barbican
|
|
namespace = barbican.certificate.plugin
|
|
namespace = barbican.certificate.plugin.snakeoil
|
|
namespace = barbican.common.config
|
|
namespace = barbican.plugin.crypto
|
|
namespace = barbican.plugin.crypto.p11
|
|
namespace = barbican.plugin.crypto.simple
|
|
namespace = barbican.plugin.dogtag
|
|
namespace = barbican.plugin.secret_store
|
|
namespace = barbican.plugin.secret_store.kmip
|
|
namespace = keystonemiddleware.auth_token
|
|
namespace = oslo.log
|
|
namespace = oslo.messaging
|
|
namespace = oslo.middleware.cors
|
|
namespace = oslo.middleware.http_proxy_to_wsgi
|
|
namespace = oslo.policy
|
|
namespace = oslo.service.periodic_task
|
|
namespace = oslo.service.sslutils
|
|
namespace = oslo.service.wsgi
|