From d4439913b1ce7cbe42be969f12208cbf6f4331ef Mon Sep 17 00:00:00 2001 From: techmaharaj Date: Wed, 22 Jun 2022 07:45:57 +0530 Subject: [PATCH] Resolved comments. --- ROADMAP.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/ROADMAP.md b/ROADMAP.md index 22bdc64..33a2eb9 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -12,11 +12,10 @@ Below is a list of features that are planned for Paralus: - **Paralus Access Plane:** Enable Paralus to provide zero trust access to resources outside of Kubernetes like Virtual Machines, Servers, Databases etc. - **Multi Factor Authentication:** Make Paralus more robust and secured by implementing multi factor authentication for users. - **Unified Error Handling:** We want to improve the way we handle errors. Make them more streamlined and standardized across all the APIs in Paralus. -- **Postgres For Audit Logs:** Make Postgres as a default database for storing audit logs to improve overall performance. Currently we are using Elasticsearch. Post the proposed change, users will be able to choose between Elasticsearch and Postgres. +- **Postgres For Audit Logs:** Make Postgres as a default database for storing audit logs to simplify the initial setup. Currently we are using Elasticsearch. Post the proposed change, users will be able to choose between Elasticsearch and Postgres. - **Easier CLI Download:** Currently the end user has to choose the CLI binary based on their system which means they can download an incompatible binary. The goal is to automatically identify user's system and provide the correct binary for download. - **Update Group Flows From OIDC Provider:** We want to add the ability to automatically configure groups in Paralus based on changes made to a user's associated group in the OIDC provider. Currently, the org admin has to manually update the groups in Paralus if there's any changes made in the OIDC provider. - **Fix Buf Lint Issues:** Paralus makes extensive use of [Protobufs](https://github.com/protocolbuffers/protobuf) across the application. The code currently isn't as per the standards and hence there are linting issues that we want to fix in the near future. -- **Implement Soft Delete Mechanism:** Paralus uses [Bun](https://github.com/uptrace/bun) to interact with database. We'd like to improve the way we handle delete operation in Paralus by implementing Bun's soft delete mechanism. - **CLI Usage Without Dashboard:** Currently the user needs to setup Paralus dashboard to use the CLI. We want to remove that and allow the users to use the CLI tool as a standalone application. While these are the planned features and enhancements, we definitely welcome suggestions and ideas from everyone. Feel free to [open an issue](https://github.com/paralus/paralus/issues).