Skip to content

Commit cdbfa7c

Browse files
committed
chore(docs): Enhance Apache Camel infra service documentation
1 parent b8caddc commit cdbfa7c

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

src/manual/endpoint-camel.adoc

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -984,6 +984,26 @@ actions:
984984
</spring:beans>
985985
----
986986

987+
Once the infrastructure service is started Citrus exposes connection settings as test variables. You can use the exposed connection settings to create proper clients that connect to the services.
988+
989+
The exposed connection settings follow a naming pattern that looks like this:
990+
991+
* `CITRUS_CAMEL_INFRA_SERVICE_<SERVICE_NAME>_<PROPERTY_NAME>`
992+
* `CITRUS_CAMEL_INFRA_SERVICE_<SERVICE_NAME>_<IMPLEMENTATION>_<PROPERTY_NAME>`
993+
994+
For instance a infrastructure service called `foo` that exposes the settings `url` and `port` expose the following test variables.
995+
996+
|===
997+
|Variable
998+
999+
| CITRUS_CAMEL_INFRA_SERVICE_FOO_URL
1000+
| CITRUS_CAMEL_INFRA_SERVICE_FOO_PORT
1001+
1002+
|===
1003+
1004+
You can now use these test variables when connecting to the service.
1005+
Please see the individual Apache Camel infrastructure services documentation to see which properties get exposed by the service.
1006+
9871007
Some infrastructure services provide multiple implementations (e.g. Kafka provides both Redpanda and Strimzi).
9881008

9891009
You may need to choose the implementation as follows:

0 commit comments

Comments
 (0)