add baseline migrations

[Marfuen]

Summary by CodeRabbit

• New Features

  • Enhanced policy management with flexible content storage and refined status options.
  • Expanded compliance and control framework that connects policies with structured requirements.
  • Improved organization profiles with unique identification enhancements.

• Chores

  • Streamlined the database schema by consolidating relationships and removing redundant elements.
  • Optimized data integrity and performance through revised indexing and relational configurations.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
app	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Feb 12, 2025 7:23pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
web	⬜️ Skipped (Inspect)			Feb 12, 2025 7:23pm

[coderabbitai]

Walkthrough

The pull request consolidates and refines the database schema by introducing a new, comprehensive migration while removing several legacy migration scripts. The new migration creates enumerated types and new tables, as well as updates existing tables by adding, dropping, or modifying columns and constraints. The deprecated migrations—once responsible for similar schema adjustments—are fully removed, streamlining the overall migration history. Additionally, the migration lock file has been deleted.

Changes

File(s)	Change Summary
packages/db/prisma/migrations/0_init/migration.sql	Introduces new enums (RequirementType, PolicyStatus); updates tables by adding a subdomain column to Organization, replacing Policy’s template with content and adding usedBy, and renaming Control’s categoryId to frameworkCategoryId; creates new tables (PolicyControl, ControlRequirement, OrganizationPolicy) with associated indexes and foreign keys.
packages/db/prisma/migrations/20250206* packages/db/prisma/migrations/20250207* packages/db/prisma/migrations/20250210* packages/db/prisma/migrations/20250211* packages/db/prisma/migrations/20250212*	Removed legacy migration scripts that previously handled column additions/drops (e.g., dropping controls, template, fileType, url), enum modifications, index/constraint adjustments, and schema refinements across Policy, Control, ControlRequirement, and OrganizationPolicy tables.
packages/db/prisma/migrations/migration_lock.toml	Deleted migration lock file that contained metadata for migration state management.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant A as Application
    participant DB as Database
    U->>A: Create new Policy with details
    A->>DB: Insert Policy record (content, usedBy)
    DB-->>A: Policy record created
    A->>DB: Link Policy with Control via PolicyControl
    DB-->>A: Linking record created
    A->>DB: Insert associated ControlRequirement records
    DB-->>A: Requirements recorded
    A->>DB: Associate Organization with Policy via OrganizationPolicy
    DB-->>A: Organization-Policy link created

Loading

Poem

Hoppin' in the fields of bytes,
New enums and tables set our sights,
Controls and policies link with grace,
Data flows in every space,
A schema dance under moonlit night,
I'm a rabbit celebrating this upgrade—bright!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2529785 and 5dffe74.

📒 Files selected for processing (14)

• packages/db/prisma/migrations/0_init/migration.sql (12 hunks)
• packages/db/prisma/migrations/20250206224138_add_controls_to_policies/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250206230606_add_requirements_to_controls/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250206231115_simplify_controls_table/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250207011314_add_policy_id/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250210204644_add_new_requirement_types/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250210212236_connect_category_to_controls/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250210214327_add_usedBy_to_policies/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250210222417_change_used_by_datatype/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250211190006_add_organization_policy_join_table/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250211223842_policy_column_change_type/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250211224712_policy_column_change/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250212175319_add_content_to_organization_policy/migration.sql (0 hunks)
• packages/db/prisma/migrations/migration_lock.toml (0 hunks)

💤 Files with no reviewable changes (13)

• packages/db/prisma/migrations/20250206224138_add_controls_to_policies/migration.sql
• packages/db/prisma/migrations/20250207011314_add_policy_id/migration.sql
• packages/db/prisma/migrations/migration_lock.toml
• packages/db/prisma/migrations/20250211224712_policy_column_change/migration.sql
• packages/db/prisma/migrations/20250210204644_add_new_requirement_types/migration.sql
• packages/db/prisma/migrations/20250210214327_add_usedBy_to_policies/migration.sql
• packages/db/prisma/migrations/20250212175319_add_content_to_organization_policy/migration.sql
• packages/db/prisma/migrations/20250210222417_change_used_by_datatype/migration.sql
• packages/db/prisma/migrations/20250206231115_simplify_controls_table/migration.sql
• packages/db/prisma/migrations/20250211190006_add_organization_policy_join_table/migration.sql
• packages/db/prisma/migrations/20250210212236_connect_category_to_controls/migration.sql
• packages/db/prisma/migrations/20250211223842_policy_column_change_type/migration.sql
• packages/db/prisma/migrations/20250206230606_add_requirements_to_controls/migration.sql

🔇 Additional comments (6)

packages/db/prisma/migrations/0_init/migration.sql (6)

13-15: LGTM! Well-defined enum types.

The new enum types RequirementType and PolicyStatus are well-structured with clear, comprehensive values that follow a logical progression.

Also applies to: 61-63

---

114-114: LGTM! Proper subdomain implementation.

The subdomain column in the Organization table is correctly implemented with a unique constraint to prevent duplicates.

Also applies to: 629-631

---

193-194: LGTM! Well-structured Control table modifications.

The Control table changes are properly implemented with:

• Optional domain field
• Indexed frameworkCategoryId with appropriate foreign key constraint

Also applies to: 671-672, 906-907

---

529-531: Consider adding validation for JSONB columns.

While using JSONB for content and usedBy provides flexibility, consider implementing application-level validation to ensure data consistency.

Please ensure that:

1. The application validates the structure of JSON data before insertion
2. Migrations handle the conversion of existing data to the new format
3. Queries properly handle potential NULL or malformed JSON values

---

573-606: LGTM! Well-designed new tables with proper relationships.

The new tables are well-structured with:

• Appropriate primary and foreign keys
• Proper indexes for performance
• Clear relationships between entities
• Consistent naming conventions

---

860-874: LGTM! Comprehensive indexing strategy.

The indexing strategy is well-designed with:

• Appropriate unique constraints to prevent duplicates
• Supporting indexes for foreign keys
• Proper cascade delete behaviors

Also applies to: 1088-1105

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.