barbican VERSION - en to en_GB translation catalogue (13 entries)

en: >>>>> Task exception seen for synchronous task invocation, so handling exception to mimic asynchronous behavior.
en_GB: >>>>> Task exception seen for synchronous task invocation, so handling exception to mimic asynchronous behaviour.

en: Could not find key labeled {0}
en_GB: Could not find key labelled {0}

en: Failed to bind kek metadata for plugin: {name}
en_GB: Failed to bind KEK metadata for plugin: {name}

en: Internal name used to identifysecretstore_plugin
en_GB: Internal name used to identify secretstore_plugin

en: Keystone notification queue topic name. This name needs to match one of values mentioned in Keystone deployment's 'notification_topics' configuration e.g.    notification_topics=notifications,     barbican_notificationsMultiple servers may listen on a topic and messages will be dispatched to one of the servers in a round-robin fashion. That's why Barbican service should have its own dedicated notification queue so that it receives all of Keystone notifications. Alternatively if the chosen oslo.messaging backend supports listener pooling (for example rabbitmq), setting a non-default 'pool_name' option should be preferred.
en_GB: Keystone notification queue topic name. This name needs to match one of values mentioned in Keystone deployment's 'notification_topics' configuration e.g.    notification_topics=notifications,     barbican_notificationsMultiple servers may listen on a topic and messages will be dispatched to one of the servers in a round-robin fashion. That's why Barbican service should have its own dedicated notification queue so that it receives all of Keystone notifications. Alternatively if the chosen oslo.messaging backend supports listener pooling (for example RabbitMQ), setting a non-default 'pool_name' option should be preferred.

en: Maximum allowed http request size against the barbican-api.
en_GB: Maximum allowed HTTP request size against the Barbican-api.

en: Period in seconds after which SQLAlchemy should reestablish its connection to the database. MySQL uses a default `wait_timeout` of 8 hours, after which it will drop idle connections. This can result in 'MySQL Gone Away' exceptions. If you notice this, you can lower this value to ensure that SQLAlchemy reconnects before MySQL can drop the connection.
en_GB: Period in seconds after which SQLAlchemy should re-establish its connection to the database. MySQL uses a default `wait_timeout` of 8 hours, after which it will drop idle connections. This can result in 'MySQL Gone Away' exceptions. If you notice this, you can lower this value to ensure that SQLAlchemy reconnects before MySQL can drop the connection.

en: Pool name for notifications listener. Setting this to a distinctive value will allow barbican notifications listener to receive its own copy of all messages from the topic without without interfering with other services listening on the same topic. This feature is supported only by some oslo.messaging backends (in particilar by rabbitmq) and for those it is preferrable to use it instead of separate notification topic for barbican.
en_GB: Pool name for notifications listener. Setting this to a distinctive value will allow barbican notifications listener to receive its own copy of all messages from the topic without without interfering with other services listening on the same topic. This feature is supported only by some oslo.messaging backends (in particular by RabbitMQ) and for those it is preferable to use it instead of separate notification topic for barbican.

en: Project cleanup via Keystone notifications
en_GB: Project clean-up via Keystone notifications

en: SSL version, maps to the module ssl's constants
en_GB: SSL version, maps to the module SSL's constants

en: True enables keystone notification listener  functionality.
en_GB: True enables Keystone notification listener  functionality.

en: True enables requeue feature in case of notification processing error. Enable this only when underlying transport supports this feature.
en_GB: True enables re-queue feature in case of notification processing error. Enable this only when underlying transport supports this feature.

en: url is required
en_GB: URL is required
