List view
The Control Center UI needs to be reorganized and optimized for better scalability, especially regarding the routing and the connectors' form.
No due date•3/3 issues closed- No due date•6/6 issues closed
Parent issue: https://github.com/airyhq/airy/issues/3464
No due date•5/5 issues closedRelated to milestone https://github.com/airyhq/airy/milestone/36, here we will create a new method to install Airy. This is a necessary step to decoupling the Airy CLI from Kubernetes (#36) and allows us to create a maintainable way to deploy Airy on different cloud providers on clusters as well as virtual machines.
No due date•11/11 issues closed- No due date•6/6 issues closed
- No due date•3/3 issues closed
Currently, we support text, emojis, and templates in the Airy Inbox and the Live Chat Plugin. We should also support media attachments.
No due date•12/12 issues closedThe issues included in this milestone will be used to dictate the core UI in Airy Inbox
No due date•5/5 issues closedCurrently the Airy Core platform stores users in a SQL database and manages users. There are a few reasons why we want to change this: - The cloud offering (or any other core user) will also maintain users. Translating their authorization to core is complex and expensive. - Using an authentication standard over custom auth endpoints is preferable for security reasons. - It’s a use case that’s unrelated to messaging
No due date•7/7 issues closed- No due date•12/12 issues closed
As a next step for the Airy CLI, we need to build the AWS provider so when executing the following ``` airy create --provider=aws ``` The result will be a reachable EKS cluster on AWS, with a functional airy core instance
No due date•5/5 issues closed- No due date•6/6 issues closed
Create tests for all parts of the system
No due date•14/14 issues closedCreating a running Airy Core platform, both locally and in the cloud with the `airy create` CLI command.
No due date•11/11 issues closed- No due date•6/6 issues closed
Original issue https://github.com/airyhq/airy/issues/863 The ultimate goal is to streamline metadata to clients, providing a standardized way of consuming and updating metadata.
No due date•9/9 issues closedIn order to enhance overall experience, we need to clearly provide requirements for suggested responses.
No due date•5/5 issues closed- No due date•50/50 issues closed
In order to enhance overall experience, we need to provide CRUD endpoints for templates and a "templates search" endpoint.
No due date•6/6 issues closedWe need to offer the ability to connect channels such as WhatsApp, SMS, GBM, Airy Live Chat, and Facebook Messenger. We also need to offer the ability to connect several phone numbers for WhatsApp and SMS, several Facebook pages, and several Airy Live Chats - which can all be managed within Admin.
No due date•11/11 issues closedWe want to support more type of messages without having to maintain their data model explicitly.
No due date•27/27 issues closedSteps to make the Airy Kubernetes controller production ready, so that it works properly with Airy resources, but also doesn't that it doesn't affect the other Kubernetes resources and the environment it is installed in.
No due date•2/2 issues closedWe need to fetch or process source profile information for contacts. We also need to support media URLs for some of this contact information. The content of the source media URLs needs to be fetched, stored, and made accessible on the Airy Core Platform, because they expire. This will also set us up for sending media to sources down the road.
No due date•6/6 issues closedThe UI of the Airy Core Platform
No due date•15/15 issues closedAllow users to connect a Twilio account and handle in- and outbound SMS and Whatsapp traffic.
No due date•8/8 issues closed- No due date•8/8 issues closed
Add and adapt the existing chat plugin.
No due date•3/3 issues closedWe want to make our system as developer friendly as possible. One way to achieve it is to introduce a command line application that simplifies interacting with the system.
No due date•7/7 issues closed- No due date•7/7 issues closed
As the core platform has a non trivial number of components, testing for regression and performance is a very costly process without some automation. The goal of this milestone is to put in place a few tools that simplify and automate testing the whole runtime and its features
No due date•3/3 issues closedCurrently, we serve the message content as the source string we ingest and store (see https://docs.airy.co/api/http#messages). Proposal: 1) Use the existing content mapping library in `backend/lib/mapping` to map this message content to a schema (`co.airy.mapping.model`) when we return it in endpoints like `messages.list` 2) Automatically generate Typescript definitions from `co.airy.mapping.model` using e.g. https://github.com/vojtechhabarta/typescript-generator
No due date•2/2 issues closed- Improve how we build and test the whole codebase - Automate pushing docker images
No due date•8/8 issues closedWe want to show a demo application with features from Inbox and Admin with open source features.
No due date•9/9 issues closedOptimize the bootstrap process for the Airy Core Platform. Related to the optimization of the underlying OS, Minikube, the used Docker images as well as the packaging process before publishing the final image to s3.
No due date•12/12 issues closed