SebastianStehle/omnisaas

AI Summary: Integrate a billing provider into the OmniSaaS platform. This involves creating Temporal workflows for hourly usage tracking and monthly invoicing, building an abstraction layer for different billing providers, and developing user and admin interfaces to display billing information and manage invoices. The integration must also enforce billing information entry before resource creation and provide links to external billing portals.

AI Summary: Implement a team activity log for OmniSaaS, tracking deployments and team updates. This involves adding logging functionality to record deployment updates and team changes, creating an aggregated view of these logs, and designing the log messages for future localization.

AI Summary: Implement functionality in the OmniSaaS backend to allow team administrators to rename their teams. This involves updating the backend API to handle team renaming requests, potentially modifying the database schema to accommodate the change, and ensuring appropriate authorization checks are in place. Frontend changes may also be necessary to reflect the updated team name in the user interface.

AI Summary: Implement health checks for resources within the OmniSaaS platform. This involves extending the deployment definition schema to include health check configurations, creating a Temporal workflow to execute these checks, storing health check results, and displaying this information in the UI. The task also requires making the health check interval and number of tests configurable.

AI Summary: Develop an admin interface to manage deployments within the OmniSaaS platform. This involves listing all deployments with search and pagination, providing detailed views of individual deployments including status, connection information, and the deployment's YAML configuration.

AI Summary: The task is to determine the best method for creating domains within the OmniSaaS platform, considering integration with Helm charts and Docker Compose. This involves deciding whether domain creation should be handled directly within the Helm chart, as a separate action, or through another mechanism, ensuring seamless integration with the existing deployment process.

AI Summary: Create GitHub Actions workflows to build Docker images for the OmniSaaS backend and worker services. This involves configuring the workflows to handle dependencies like Kubernetes, Helm, and Docker, and potentially managing different build environments or stages.

AI Summary: The task requires creating a GitHub Actions workflow that provisions an S3-compatible storage resource on DigitalOcean Spaces if it doesn't already exist. The action should then return the necessary connection details (e.g., endpoint, access key, secret key) to be used within the OmniSaaS deployment context. This mirrors functionality already implemented for Vultr.

AI Summary: The task requires creating a new action within the OmniSaaS platform to handle the deployment of Docker Compose files. This action should integrate with at least two cloud providers: Vultr and DigitalOcean. The implementation will likely involve interacting with their respective APIs to provision and manage resources defined in the Docker Compose files.

AI Summary: Develop a user interface for managing teams within the OmniSaaS platform. This includes listing existing team members, adding new members via email invitation, removing members, and displaying a warning about direct resource access limitations. Optional enhancements involve exploring notification methods (email, Novu, Notifo, or in-app).