nicolaferraro edited a comment on issue #2690:
URL: https://github.com/apache/camel-k/issues/2690#issuecomment-943121484
Hi, the binding should be ok, the only thing is that you may want to specify
the cloud event type in order to subscribe to it at destination. In the
KameletBinding world, you do it like this:
```yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: mqtt-source-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: mqtt-source
properties:
brokerUrl: "tcp://mosquitto:1883"
topic: "mytopic"
sink:
ref:
kind: Broker
apiVersion: messaging.knative.dev/v1
name: default
properties:
type: mqtt # <-- here
```
For 2, sure. Usually it's possible to do the reverse with switching source
and sink (and changing the kamelet type), but apparently we forgot to provide a
`mqtt-sink` kamelet (opened
https://github.com/apache/camel-kamelets/issues/544).
But you can still use the plain Camel paho component in URI. Like:
```yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: mqtt-sink-binding
spec:
source:
ref:
kind: Broker
apiVersion: messaging.knative.dev/v1
name: default
properties:
type: mqtt
sink:
uri: paho:yourothertopic
properties:
brokerUrl: "tcp://mosquitto:1883"
```
Let me know if it works. We should be able to provide a mqtt-sink in next
version
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
