From 32f9807d0caeec17054534f6388d4bb89f4a6084 Mon Sep 17 00:00:00 2001 From: Nelson Parente Date: Wed, 8 Jul 2026 15:19:55 +0100 Subject: [PATCH 1/2] docs: document Pulsar listenerName metadata field Documents the listenerName field added to the Pulsar pubsub component in dapr/components-contrib#4386, which exposes the pulsar-client-go ListenerName option for advertisedListeners / multi-listener broker topologies. Ships in Dapr 1.19. Signed-off-by: Nelson Parente --- .../components-reference/supported-pubsub/setup-pulsar.md | 1 + 1 file changed, 1 insertion(+) diff --git a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md index 338324afa82..67bace98b80 100644 --- a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md +++ b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md @@ -78,6 +78,7 @@ The above example uses secrets as plain strings. It is recommended to use a [sec | Field | Required | Details | Example | |--------------------|:--------:|---------|---------| | host | Y | Address of the Pulsar broker. Default is `"localhost:6650"` | `"localhost:6650"` OR `"http://pulsar-pj54qwwdpz4b-pulsar.ap-sg.public.pulsar.com:8080"`| +| listenerName | N | Configures the listener name the Pulsar client sends to the broker for connection redirects. Brokers configured with `advertisedListeners` resolve the redirect target using the matching named listener, enabling cross-network topologies (multi-cluster, internal/external endpoints) without a Pulsar proxy. See [Pulsar Multiple Advertised Listeners](https://pulsar.apache.org/docs/3.0.x/concepts-multiple-advertised-listeners/). When unset, behavior is unchanged. | `"external"` | | enableTLS | N | Enable TLS. Default: `"false"` | `"true"`, `"false"` | | tenant | N | The topic tenant within the instance. Tenants are essential to multi-tenancy in Pulsar, and spread across clusters. Default: `"public"` | `"public"` | | consumerID | N | Used to set the subscription name or consumer ID. | Can be set to string value (such as `"channel1"` in the example above) or string format value (such as `"{podName}"`, etc.). [See all of template tags you can use in your component metadata.]({{% ref "component-schema.md#templated-metadata-values" %}}) From 21692f6f07d247884028d25b3fdf0346d379ec44 Mon Sep 17 00:00:00 2001 From: Nelson Parente Date: Wed, 8 Jul 2026 16:24:12 +0100 Subject: [PATCH 2/2] docs: clarify Pulsar listenerName is the client-side listener selector Address review feedback: distinguish the client-side listenerName (a single listener name matching one in the broker's advertisedListeners) from the broker-side advertisedListeners/internalListenerName config, note that internal/external are operator-chosen conventions rather than fixed values, and state the default. Signed-off-by: Nelson Parente --- .../components-reference/supported-pubsub/setup-pulsar.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md index 67bace98b80..c55dbb4fe51 100644 --- a/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md +++ b/daprdocs/content/en/reference/components-reference/supported-pubsub/setup-pulsar.md @@ -78,7 +78,7 @@ The above example uses secrets as plain strings. It is recommended to use a [sec | Field | Required | Details | Example | |--------------------|:--------:|---------|---------| | host | Y | Address of the Pulsar broker. Default is `"localhost:6650"` | `"localhost:6650"` OR `"http://pulsar-pj54qwwdpz4b-pulsar.ap-sg.public.pulsar.com:8080"`| -| listenerName | N | Configures the listener name the Pulsar client sends to the broker for connection redirects. Brokers configured with `advertisedListeners` resolve the redirect target using the matching named listener, enabling cross-network topologies (multi-cluster, internal/external endpoints) without a Pulsar proxy. See [Pulsar Multiple Advertised Listeners](https://pulsar.apache.org/docs/3.0.x/concepts-multiple-advertised-listeners/). When unset, behavior is unchanged. | `"external"` | +| listenerName | N | Selects which of a broker's [advertised listeners](https://pulsar.apache.org/docs/3.0.x/concepts-multiple-advertised-listeners/) the client connects through, for brokers that expose more than one network endpoint (for example separate internal and external addresses). The value is a single listener **name** that must match one the broker operator defined in its `advertisedListeners` configuration — it is *not* the `:pulsar://:` address map, which is configured on the broker, not in Dapr. Listener names are chosen by the operator; `internal` and `external` are common conventions rather than a fixed set of values. Default: `""` (no listener name is sent and the broker's default listener is used, so behavior is unchanged). | `"external"` | | enableTLS | N | Enable TLS. Default: `"false"` | `"true"`, `"false"` | | tenant | N | The topic tenant within the instance. Tenants are essential to multi-tenancy in Pulsar, and spread across clusters. Default: `"public"` | `"public"` | | consumerID | N | Used to set the subscription name or consumer ID. | Can be set to string value (such as `"channel1"` in the example above) or string format value (such as `"{podName}"`, etc.). [See all of template tags you can use in your component metadata.]({{% ref "component-schema.md#templated-metadata-values" %}})