Christoph Proeschel

## Describe the bug When following [this guide](https://blog.airy.co/streaming-data-airy-confluent/#step-4-configure-existing-airy-to-use-confluent) the auth jaas value does [not get templated ](https://github.com/airyhq/airy/blob/6efcc571e21e979c6e96daf27400b436388e5351/infrastructure/helm-chart/templates/config/kafka.yaml#L8) causing the topics provisioning to fail.

[Parent issue](https://github.com/airyhq/airy/issues/3464) There should be a new endpoint (or reusing an existing endpoint) ready to receive events from the source (payloads here: https://developers.facebook.com/docs/whatsapp/cloud-api/webhooks/payload-examples)

[Parent issue](https://github.com/airyhq/airy/issues/3464) We should be able to mark messages as read in the source (https://developers.facebook.com/docs/whatsapp/cloud-api/guides/mark-message-as-read)

[Parent issue](https://github.com/airyhq/airy/issues/3464) We should be able to send messages to the source (https://developers.facebook.com/docs/whatsapp/cloud-api/guides/send-messages) Should also support template messages: https://developers.facebook.com/docs/whatsapp/cloud-api/guides/send-message-templates

## Describe the bug The `co.airy.core.webhook.consumer.ConsumerTest` fails inconsistently both on CI and on development machines. This causes a delay in the process. ## To Reproduce Run the test a couple...

## This is how we could improve the [documentation](https://docs.airy.co): Now that Airy can be connected to a remote Kafka it would be useful to have a guide for how one...

SDK for building and deploying custom sources

2

## Is your feature request related to a problem? Please describe. To deploy custom user code to the Airy cluster we need to integrate the runtimes with our existing Kubernetes...

Research swagger for API and client generation

1

**Current state** Airy Core has ~41 API routes that are accessible to clients. Each of them requires payload definitions for clients and standard markdown documentation. We have a typescript and...

prerequisite for #3536

Document how source content works

3

**Current state** We have a "as transparent as possible" approach to dealing with source messages and event payloads, which we acquired through years of operating a multi-source streaming messaging system....