Diko was able to add the [database] header and get things working.
However, when I updated the template to use section-database which includes the [database] header the db sync (barbican-manage db upgrade) fails as it attempts to use SQLite.
Upstream documentation even for the latest version of Barbican seems to indicate sql_connection in the [DEFAULT] header space [1].
It is theoretically possible the barbican-worker expects something different from what barbican-mage expects. It may not hurt to have both in the template. More investigation is necessary.
This is an interesting bug.
Diko was able to add the [database] header and get things working.
However, when I updated the template to use section-database which includes the [database] header the db sync (barbican-manage db upgrade) fails as it attempts to use SQLite.
Upstream documentation even for the latest version of Barbican seems to indicate sql_connection in the [DEFAULT] header space [1].
It is theoretically possible the barbican-worker expects something different from what barbican-mage expects. It may not hurt to have both in the template. More investigation is necessary.
[0] https:/ /review. opendev. org/c/openstack /charm- barbican/ +/801361 /docs.openstack .org/barbican/ latest/ sample_ config. html
[1] https:/