Please enable JavaScript.

Coggle requires JavaScript to display documents.

LLM Setting Page Design, NextJS, LLM Setting Page Specification, Proposals…

- - - - Create layout component
        
        Create Server page to fetch LLM settings
        
        this follows settings/engine/page.tsx's convention
        
        Create main client Form component
        
        Populate with children from the linked form branch
    - - Components
        
        Create input components for abstract env variables.
        
        Reuse existing vault/password inputs
        
        Create Snowflake specific components
        
        Create object Mapping for the inputs to be rendered appropriately given the specified provider.
        
        apps/web/app/[locale]/control-center/settings/data-warehouses/shared/password-schema.ts
      - Create Form Layout/Wrapper
        
        Create Submission handler
        
        to call server action, probably a mutation.
        
        Hook up logic and validation
      - Form branch completes the LLM Page, but work can be done in sync
  - - - Hook up to LLM Endpoints
      - Copy setting/engine/action.ts action
- - - - Hook up Schema to the database.schema.ts
      - Create Migrations
        
        drizzle official docs/migrations
      - Create table schema for current snowflake provider and planned future providers
  - - - Structure
        
        With EnvService to read flag
        
        Connection for Postgres
      - Methods
        
        create setting
        
        Do not return password
        
        Encrypt into DB
        
        read setting
        
        Decrypt from DB
        
        This is actually two different things. The read endpoint should never return the password, so no need to decrypt it here.
        
        However, we will need a method to grab the decrypted password so we can use it when connecting to Snowflake. I just wanted to reinforce this
        
        update setting
        
        Do not return password
        
        Encrypt into DB
        
        delete setting
        
        Test connection
        
        return request.body
    - - Register Controller
      - Register Service
    - - Test connection
      - delete
      - update
      - read
      - create

Proposals

Two JSON column that accepts objects that represent "secretProperties" and "extraProperties". The purpose is that "secretProperties" are encrypted.

function(extraProperties: Record<string, string> secretProperties: Record<string, string>) {

    const encryptedSecretProperties = encrypt(secretProperties);

    / / Write to DB
    write(JSON.stringify(
        {
            secretProperties: encryptedSecretProperties,
            extraProperties
        }));
    }

function(extraProperties: Record<string, string> secretProperties: Record<string, string>) {

    const encryptedSecretProperties = encrypt(secretProperties);

     //    Write to DB
    write(JSON.stringify(
         {
            secretProperties: encryptedSecretProperties
        }
        ), 
        JSON.stringify(
            extraProperties
         )); 
    }

Schema

import { uuid, pgSchema, jsonb} from 'drizzle-orm/pg-core';

export const reposApiSchema = pgSchema('api');

const table = pgTable('table', {
  id: uuid('id').defaultRandom().primaryKey(),
  secretProperties: jsonb('secretProperties'),
  extraProperties: jsonb('extraProperties'),
});