pantheon/hestia
2
0
Fork 0
Code Issues 23 Pull requests Projects Releases Packages Wiki Activity Actions

41 create tenant twilio config #62

Merged
BenjaminPalko merged 20 commits from 41-create-tenant-twilio-config into master 2025-01-26 23:36:06 -05:00
Conversation 1 Commits 20 Files changed 24 +17 -8
1 changed files with 17 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit cb645e43a9 - Show all commits

25
prisma/schema.prisma
View file

@ -32,18 +32,27 @@ model User {
} }
model Tenant { model Tenant {
id String @id @default(uuid()) id String @id @default(uuid())
name String clerkOrganizationId String @unique
slug String @unique
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
clerkOrganizationId String @unique
users User[] users User[]
tenantConfig TenantConfig?
name String
slug String @unique
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
} }
model TenantConfig { model TenantConfig {
tenantId String @id id String @id @default(uuid())
tenant Tenant @relation(fields: [tenantId], references: [id])
tenantId String @unique
accountSID String accountSID String
authToken String authToken String
phoneNumber String phoneNumber String
piopi commented 2025-01-17 11:52:58 -05:00 (Migrated from github.com)
Review
Copy link

Not a fan of calling this TenantConfig while it contains twillio specific fields, if you have a new integration like sendgrid, will you just add a new column here? It doesn't feel scalable, I think you could either rename this to TwillioTenantConfig, if you don't wanna deal with it now or have a generic way to store integration credentials. Like have two column, integrationName, integrationValues (JSON column)

Not a fan of calling this TenantConfig while it contains twillio specific fields, if you have a new integration like sendgrid, will you just add a new column here? It doesn't feel scalable, I think you could either rename this to TwillioTenantConfig, if you don't wanna deal with it now or have a generic way to store integration credentials. Like have two column, integrationName, integrationValues (JSON column)
piopi commented 2025-01-17 11:53:52 -05:00 (Migrated from github.com)
Review
Copy link

and use Zod for validation

and use Zod for validation
}
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
}