Skip to content

Commit

Permalink
Merge pull request #28069 from gsmet/fix-rabbitmq-reference
Browse files Browse the repository at this point in the history
Fix some minor issues in rabbitmq-reference.adoc
  • Loading branch information
geoand authored Sep 19, 2022
2 parents 5faa68d + c28fcf7 commit d06ad47
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/src/main/asciidoc/rabbitmq-reference.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -222,7 +222,7 @@ three strategies, controlled by the failure-strategy channel setting:

=== Serialization

When sendingWhen sending a `Message<T>`, the connector converts the message into a RabbitMQ Message. The payload is converted to the RabbitMQ Message body.
When sending a `Message<T>`, the connector converts the message into a RabbitMQ Message. The payload is converted to the RabbitMQ Message body.

[options=header]
|===
Expand Down Expand Up @@ -446,8 +446,8 @@ Next we configure the `rabbitmq` credentials provider. The `credentials-role` op
role we created in Vault, in our case `my-role`. The `credentials-mount` option must be set to `rabbitmq`.
[source, properties]
----
quarkus.vault.credentials-provider.rabbitmq.credentials-role = my-role
quarkus.vault.credentials-provider.rabbitmq.credentials-mount = rabbitmq
quarkus.vault.credentials-provider.rabbitmq.credentials-role=my-role
quarkus.vault.credentials-provider.rabbitmq.credentials-mount=rabbitmq
----

NOTE: The `credentials-mount` is used directly as the mount of the secret engine in Vault. Here we are using
Expand Down

0 comments on commit d06ad47

Please sign in to comment.