Goal v1 Internal

This document plans out the required steps for the first internal use of project vyndara for arematics.

Legend

• Red = Next Up – Has to be done next to proceed with other tasks
• Orange = Ready – ready to take off planning is ready and can be started
• Blocked – Waits for other systems, tasks or designs it has a dependency on
• – Done
• – Todo

Everything else can be done when other stuff is finished

General System Adjustments

• Remove db name field usage for expanding
• Fix orm system test errors
• Application Level integration
• Rest Service
  • Improve error handling on checks / mappers
  • Support sort by on pages
  • simple query api - Waiting for Entity Definitions because they need to integrate into it
  • Fix broken expansion of one to many to many to one in roles ↔ permissions
• Country specifics - Waiting for Tenant Configuration
• Handle database migrations in a better way - Waiting for Tenant Configuration

Frontend

• Is shit overall need to design first and then plan out steps
• Frontend
  • Finalize Roles
    • Role Search
    • Modify Description
    • Add Permissions to a Role
  • Impl Rights
    • Rights Search
    • List of roles assigned to the right
    • Assign to other roles also there
    • Adjust name
    • Create new rights
  • Apps support
    • List of apps and also app select becomes really fetched
    • App registration (currently only add, vault write and stuff is done manual until kubernetes handler is ready)
• Organization setup process
• Integrate Sidebase Nuxt Auth and provide sso and session refreshing - SSO only possible with redis, will be checked in a later state else it seems to work
• Create ASQL (Arematics Service Query Language)

Entities

• Make the role ↔ entity permission many to many a custom join table with the level entry - Little change, is one to many to many to one so its working with versioning right now
• Entity Definitions
  • Definition based access validation handling (block, ignore)
  • Change from type condition to type filters and allow multiple filters to support min max on numbers but all filters need to be based on the type definition
• Entities endpoint
  • General entity crud operations
  • Rule setup about handling access validation for customers (block, ignore not allowed fields on create/update)
  • Field based access validation on inputs and outputs
• Virtual Rest support
  • Support custom endpoints based on entity definition with custom filters

Manager

• Organization setup and branding features
  • Organization register api
• License validation and checks
• Runner licensing (Only specific hardware can run a service)
• Vault integration for updating secrets