Skip to content

Milestones

List view

  • Introduce custom apps in Airy

    We would like to have the possibility to deploy custom code that operates on top of the existing Airy platform. We can have types of apps (ex. Python, Typescript). Then an user should be able to package the code into a container and deploy a helm chart with all the resources (workloads, services, ingresses).

    No due date
    •0/1 issues closed
    0% complete1 open0 closed

  • Introduce sources-slack component

    Creating an open source connector for Slack.

    No due date
    •0/3 issues closed
    0% complete3 open0 closed

  • Decouple the Airy CLI from Kubernetes

    Currently the Airy CLI is talking to Kubernetes, to create the ConfigMaps needed to start or stop the components. This creates a need for configuring Kubernetes access for the CLI. Even though that solves the authentication issue, we want instead to make the CLI talk to the endpoints inside Airy Core.

    No due date
    •6/9 issues closed
    66% complete3 open6 closed

  • Custom sources

    We use Kafka for highly scalable real-time data ingestion and fan-out. The Java library Kafka Streams allows us to write high-performance, fault-tolerant stream processing apps, and real-time APIs. Therefore all our (source) backends are written in Java (+ Spring). Duplicated streaming code despite similar source interfaces Adding new sources can be time-consuming We want to build more sources quickly by providing users with a code API to add sources quickly, so without the need to understand and writing streaming apps.

    No due date
    •3/6 issues closed
    50% complete3 open3 closed

  • Typescript Http Client Library

    follow-up of #591 - Typescript Http Client Library. Produce a public library that is compatible with both the browser and Node.js and that is released as an NPM package.

    No due date
    •14/15 issues closed
    93% complete1 open14 closed