[PR requested change] [Docs] Config props reduction (~50% reduction)

Author: onobc

spring-boot-project/spring-boot-docs/src/docs/asciidoc/messaging/pulsar.adoc

@@ -20,6 +20,10 @@ This can be adjusted by setting the configprop:spring.pulsar.client.service-url[
 
 TIP: The value must be a valid https://pulsar.apache.org/docs/client-libraries-java/#connection-urls[Pulsar Protocol] URL
 
+You can configure the client by specifying any of the `spring.pulsar.client.*` prefixed application properties.
+
+If you need more control over the configuration, consider registering one or more `PulsarClientBuilderCustomizer` beans.
+
 [[messaging.pulsar.connecting.auth]]
 ==== Authentication
 To connect to a Pulsar cluster that requires authentication, you need to specify which authentication plugin to use by setting the `authPluginClassName` and any parameters required by the plugin.
@@ -82,6 +86,8 @@ The `PulsarTemplate` relies on a `PulsarProducerFactory` to create the underlyin
 Spring Boot auto-configuration also provides this producer factory, which by default, caches the producers that it creates.
 You can configure the producer factory and cache settings by specifying any of the `spring.pulsar.producer.\*` and `spring.pulsar.producer.cache.*` prefixed application properties.
 
+If you need more control over the producer factory configuration, consider passing in a `ProducerBuilderCustomizer` when sending a message.
+
 [[messaging.pulsar.sending-reactive]]
 === Sending a Message Reactively
 When the Reactive auto-configuration is activated, Spring's `ReactivePulsarTemplate` is auto-configured, and you can use it to send messages, as shown in the following example:
@@ -92,6 +98,7 @@ The `ReactivePulsarTemplate` relies on a `ReactivePulsarSenderFactory` to actual
 Spring Boot auto-configuration also provides this sender factory, which by default, caches the producers that it creates.
 You can configure the sender factory and cache settings by specifying any of the `spring.pulsar.reactive.sender.\*` and `spring.pulsar.reactive.sender.cache.*` prefixed application properties.
 
+If you need more control over the sender factory configuration, consider passing in a `MessageSpecBuilderCustomizer` when sending a message.
 
 [[messaging.pulsar.receiving]]
 === Receiving a Message
@@ -103,6 +110,8 @@ include::code:MyBean[]
 Spring Boot auto-configuration provides all the components necessary for `PulsarListener`, such as the `PulsarListenerContainerFactory` and the consumer factory it uses to construct the underlying Pulsar consumers.
 You can configure these components by specifying any of the `spring.pulsar.listener.\*` and `spring.pulsar.consumer.*` prefixed application properties.
 
+If you need more control over the consumer factory configuration, consider registering a `ConsumerBuilderCustomizer` bean and specifying it on the `consumerCustomizer` attribute of the `@PulsarListener` annotation.
+
 [[messaging.pulsar.receiving-reactive]]
 === Receiving a Message Reactively
 When the Apache Pulsar infrastructure is present and the Reactive auto-configuration is activated, any bean can be annotated with `@ReactivePulsarListener` to create a reactive listener endpoint.
@@ -113,6 +122,7 @@ include::code:MyBean[]
 Spring Boot auto-configuration provides all the components necessary for `ReactivePulsarListener`, such as the `ReactivePulsarListenerContainerFactory` and the consumer factory it uses to construct the underlying reactive Pulsar consumers.
 You can configure these components by specifying any of the `spring.pulsar.reactive.listener.\*` and `spring.pulsar.reactiver.consumer.*` prefixed application properties.
 
+If you need more control over the consumer factory configuration, consider registering a `ReactiveMessageConsumerBuilderCustomizer` bean and specifying it on the `consumerCustomizer` attribute of the `@ReactivePulsarListener` annotation.
 
 [[messaging.pulsar.reading]]
 === Reading a Message
@@ -127,6 +137,7 @@ include::code:MyBean[]
 The `@PulsarReader` relies on a `PulsarReaderFactory` to create the underlying Pulsar reader.
 Spring Boot auto-configuration provides this reader factory which can be customized by setting any of the `spring.pulsar.reader.*` prefixed application properties.
 
+If you need more control over the reader factory configuration, consider registering a `ReaderBuilderCustomizer` bean and specifying it on the `readerCustomizer` attribute of the `@PulsarReader` annotation.
 
 [[messaging.pulsar.reading-reactive]]
 === Reading a Message Reactively
@@ -137,6 +148,16 @@ include::code:MyBean[]
 
 Spring Boot auto-configuration provides this reader factory which can be customized by setting any of the `spring.pulsar.reactive.reader.*` prefixed application properties.
 
+If you need more control over the reader factory configuration, consider passing in one or more `ReactiveMessageReaderBuilderCustomizer` instances when using the factory to create a reader.
 
 
 TIP: For more details on any of the above components and to discover other available features, see the Spring for Apache Pulsar {spring-pulsar-docs}[reference documentation].
+
+[[messaging.pulsar.additional-properties]]
+=== Additional Pulsar Properties
+The properties supported by auto configuration are shown in the <<application-properties#appendix.application-properties.integration, "`Integration Properties`">> section of the Appendix.
+Note that, for the most part, these properties (hyphenated or camelCase) map directly to the Apache Pulsar configuration properties.
+See the Apache Pulsar documentation for details.
+
+Only a subset of the properties supported by Pulsar are available directly through the `PulsarProperties` class.
+If you wish to tune the auto-configured components with additional properties that are not directly supported, you can use the customizer supported by each aforementioned component.