@adobe/spacecat-shared-data-access 2.109.0 → 3.0.0

package/CHANGELOG.md

@@ -1,3 +1,17 @@
+## [@adobe/spacecat-shared-data-access-v3.0.0](https://github.com/adobe/spacecat-shared/compare/@adobe/spacecat-shared-data-access-v2.109.0...@adobe/spacecat-shared-data-access-v3.0.0) (2026-02-16)
+
+### ⚠ BREAKING CHANGES
+
+* **data-access:** data-access v3 migrates from DynamoDB/ElectroDB to Postgres/PostgREST
+
+Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
+* data access v3 (#1349)
+
+### Features
+
+* data access v3 ([#1349](https://github.com/adobe/spacecat-shared/issues/1349)) ([6db6b79](https://github.com/adobe/spacecat-shared/commit/6db6b79ecb7813acad798a2435fe317cd9d1731c))
+* **data-access:** v3 Postgres/PostgREST migration ([b79725f](https://github.com/adobe/spacecat-shared/commit/b79725f6a53bc0baac14a64acd8105a3eec56d99))
+
 # [@adobe/spacecat-shared-data-access-v2.109.0](https://github.com/adobe/spacecat-shared/compare/@adobe/spacecat-shared-data-access-v2.108.0...@adobe/spacecat-shared-data-access-v2.109.0) (2026-02-16)
 
 

package/README.md

@@ -1,6 +1,11 @@
-# SpaceCat Shared Data Access
+# Spacecat Shared Data Access (v3)
 
-This Node.js module, `spacecat-shared-data-access`, is a data access layer for managing sites and their audits, leveraging Amazon DynamoDB.
+`@adobe/spacecat-shared-data-access` is the shared data-access layer used by Spacecat services.
+
+This package is **v3 Postgres-first**:
+- Primary datastore: **Postgres via PostgREST** (`@supabase/postgrest-js`)
+- Optional secondary datastore: **S3** (for `Configuration`)
+- No ElectroDB/DynamoDB runtime dependency in v3 behavior
 
 ## Installation
 
@@ -8,293 +13,303 @@ This Node.js module, `spacecat-shared-data-access`, is a data access layer for m
 npm install @adobe/spacecat-shared-data-access
 ```
 
+## What You Get
+
+The package provides:
+- `createDataAccess(config, log?, client?)`
+- `dataAccessWrapper(fn)` (default export) for Helix/Lambda style handlers
+- Entity collections/models with stable external API shape for services
+
+## Quick Start
+
+```js
+import { createDataAccess } from '@adobe/spacecat-shared-data-access';
+
+const dataAccess = createDataAccess({
+  postgrestUrl: process.env.POSTGREST_URL,
+  postgrestSchema: process.env.POSTGREST_SCHEMA || 'public',
+  postgrestApiKey: process.env.POSTGREST_API_KEY,
+  // Only needed if you use Configuration entity:
+  s3Bucket: process.env.S3_CONFIG_BUCKET,
+  region: process.env.AWS_REGION,
+}, console);
+
+const site = await dataAccess.Site.findById('0983c6da-0dee-45cc-b897-3f1fed6b460b');
+console.log(site?.getBaseURL());
+```
+
+## Configuration
+
+### `createDataAccess` config
+
+- `postgrestUrl` (required): Base URL of PostgREST server
+- `postgrestSchema` (optional): Postgres schema exposed by PostgREST, default `public`
+- `postgrestApiKey` (optional): Added as `apikey` and `Authorization: Bearer ...`
+- `postgrestHeaders` (optional): Extra headers for PostgREST client
+- `s3Bucket` (optional): Required only for `Configuration` entity
+- `region` (optional): AWS region for S3 client
+
+### Custom PostgREST client
+
+You can inject an already-constructed PostgREST client as third argument:
+
+```js
+import { PostgrestClient } from '@supabase/postgrest-js';
+import { createDataAccess } from '@adobe/spacecat-shared-data-access';
+
+const client = new PostgrestClient(process.env.POSTGREST_URL, { schema: 'public' });
+const dataAccess = createDataAccess({ postgrestUrl: process.env.POSTGREST_URL }, console, client);
+```
+
+## Wrapper Usage
+
+Default export is a wrapper that attaches `context.dataAccess`.
+
+```js
+import wrap from '@adobe/helix-shared-wrap';
+import dataAccessWrapper from '@adobe/spacecat-shared-data-access';
+
+async function run(request, context) {
+  const { dataAccess } = context;
+  const site = await dataAccess.Site.findById(request.params.siteId);
+  return {
+    statusCode: site ? 200 : 404,
+    body: site ? site.toJSON() : { error: 'not found' },
+  };
+}
+
+export const main = wrap(run)
+  .with(dataAccessWrapper);
+```
+
+The wrapper reads from `context.env`:
+- `POSTGREST_URL` (default fallback: `http://localhost:3000`)
+- `POSTGREST_SCHEMA`
+- `POSTGREST_API_KEY`
+- `S3_CONFIG_BUCKET`
+- `AWS_REGION`
+
+## Field Mapping Behavior
+
+Public model API remains camelCase while Postgres/PostgREST tables are snake_case.
+
+Examples:
+- `site.siteId` <-> `sites.id`
+- `site.baseURL` <-> `sites.base_url`
+
+The mapping is handled in the base PostgREST utilities and applied on both read and write paths.
+
 ## Entities
 
-### Sites
-- **id** (String): Unique identifier for a site.
-- **baseURL** (String): Base URL of the site.
-- **imsOrgId** (String): Organization ID associated with the site.
-- **createdAt** (String): Timestamp of creation.
-- **updatedAt** (String): Timestamp of the last update.
-- **GSI1PK** (String): Partition key for the Global Secondary Index.
-
-### SiteCandidates
-- **baseURL** (String): Base URL of the site candidate.
-- **status** (String): Status of the site candidate (PENDING, IGNORED, APPROVED, ERROR).
-- **createdAt** (String): Timestamp of creation.
-- **updatedAt** (String): Timestamp of the last update.
-- **updatedBy** (String): Slack id of the last person updated the site candidate.
-
-### Audits
-- **siteId** (String): Identifier of the site being audited.
-- **SK** (String): Sort key, typically a composite of audit type and timestamp.
-- **auditedAt** (String): Timestamp of the audit.
-- **auditResult** (Map): Results of the audit.
-- **auditType** (String): Type of the audit.
-- **expiresAt** (Number): Expiry timestamp of the audit.
-- **fullAuditRef** (String): Reference to the full audit details.
-
-### SiteTopPages
-- **siteId** (String): Identifier of the site.
-- **url** (String): URL of the top page.
-- **traffic** (Number): Traffic of the top page.
-- **source** (String): Source of the data.
-- **geo** (String): Geo of the top page.
-- **importedAt** (String): Timestamp of the import.
-
-### Organization
-- **id** (String): Unique identifier for an organization.
-- **createdAt** (String): Timestamp of creation.
-- **updatedAt** (String): Timestamp of the last update.
-
-### OrganizationIdentityProvider
-- **id** (String): Unique identifier for the identity provider.
-- **metadata** (Map): Metadata for the identity provider.
-- **provider** (String): Type of identity provider. (IMS, MICROSOFT, GOOGLE)
-- **externalId** (String): External identifier from the provider.
-- **createdAt** (String): Timestamp of creation.
-
-### TrialUser
-- **id** (String): Unique identifier for the trial user.
-- **externalUserId** (String): External user identifier.
-- **status** (String): Status of the trial user. (REGISTERED, VERIFIED, BLOCKED, DELETED)
-- **provider** (String): Type of identity provider. (IMS, MICROSOFT, GOOGLE)
-- **lastSeenAt** (String): Timestamp of last activity.
-- **createdAt** (String): Timestamp of creation.
-- **metadata** (Map): Metadata for the trial user.
-- **updatedAt** (String): Timestamp of the last update.
-
-### TrialUserActivity
-- **id** (String): Unique identifier for the trial user activity.
-- **type** (String): Type of activity performed. (SIGN_UP, SIGN_IN, CREATE_SITE, RUN_AUDIT, PROMPT_RUN, DOWNLOAD)
-- **details** (Map): Details of the activity.
-- **createdAt** (String): Timestamp of creation.
-- **productCode** (String): Product code associated with the activity. (LLMO, ASO, etc.)
-
-### Entitlement
-- **id** (String): Unique identifier for the entitlement.
-- **productCode** (String): Product code for the entitlement. (LLMO, ASO, etc.)
-- **tier** (String): Tier level of the entitlement. (FREE_TRIAL, PAID)
-- **status** (String): Status of the entitlement. (ACTIVE, SUSPENDED, ENDED)
-- **createdAt** (String): Timestamp of creation.
-- **updatedAt** (String): Timestamp of the last update.
-- **quotas** (Map): Quota information for the entitlement.
-
-### SiteEnrollment
-- **id** (String): Unique identifier for the site enrollment.
-- **status** (String): Status of the enrollment. (ACTIVE, SUSPENDED, ENDED)
-- **createdAt** (String): Timestamp of creation.
-
-### FixEntity
-- **fixEntityId** (String): Unique identifier for the fix entity.
-- **opportunityId** (String): ID of the associated opportunity.
-- **createdAt** (String): Timestamp of creation.
-- **updatedAt** (String): Timestamp of the last update.
-- **type** (String): Type of the fix entity (from Suggestion.TYPES).
-- **status** (String): Status of the fix entity (PENDING, DEPLOYED, PUBLISHED, FAILED, ROLLED_BACK).
-- **executedBy** (String): Who executed the fix.
-- **executedAt** (String): When the fix was executed.
-- **publishedAt** (String): When the fix was published.
-- **changeDetails** (Object): Details of the changes made.
-
-### Suggestion
-- **suggestionId** (String): Unique identifier for the suggestion.
-- **opportunityId** (String): ID of the associated opportunity.
-- **updatedAt** (String): Timestamp of the last update.
-- **createdAt** (String): Timestamp of creation.
-- **status** (String): Status of the suggestion (NEW, APPROVED, IN_PROGRESS, SKIPPED, FIXED, ERROR, OUTDATED, PENDING_VALIDATION, REJECTED).
-- **type** (String): Type of the suggestion (CODE_CHANGE, CONTENT_UPDATE, REDIRECT_UPDATE, METADATA_UPDATE, AI_INSIGHTS, CONFIG_UPDATE).
-- **rank** (Number): Rank/priority of the suggestion.
-- **data** (Object): Data payload for the suggestion.
-- **kpiDeltas** (Object): KPI delta information (optional).
-
-### FixEntitySuggestion
-- **suggestionId** (String): ID of the associated suggestion (primary partition key).
-- **fixEntityId** (String): ID of the associated fix entity (primary sort key).
-- **opportunityId** (String): ID of the associated opportunity.
-- **fixEntityCreatedAt** (String): Creation timestamp of the fix entity.
-- **fixEntityCreatedDate** (String): Date portion of fixEntityCreatedAt (auto-generated).
-- **createdAt** (String): Timestamp of creation.
-- **updatedAt** (String): Timestamp of the last update.
-
-## DynamoDB Data Model
-
-The module is designed to work with the following DynamoDB tables:
-
-1. **Sites Table**: Manages site records.
-2. **Audits Table**: Stores audit information for each site.
-3. **Latest Audits Table**: Holds only the latest audit for each site for quick access.
-4. **Site Candidates Table**: Manages site candidates.
-5. **Site Top Pages Table**: Stores top pages for each site.
-
-Each table is designed with scalability and efficient querying in mind, utilizing both key and non-key attributes effectively.
-
-For a detailed schema, refer to `docs/schema.json`. This schema is importable to Amazon NoSQL Workbench and used by the integration tests.
-
-## Integration Testing
-
-The module includes comprehensive integration tests embedding a local DynamoDB server with in-memory storage for testing:
+Current exported entities include:
+- `ApiKey`
+- `AsyncJob`
+- `Audit`
+- `AuditUrl`
+- `Configuration`
+- `Entitlement`
+- `Experiment`
+- `FixEntity`
+- `FixEntitySuggestion`
+- `ImportJob`
+- `ImportUrl`
+- `KeyEvent`
+- `LatestAudit`
+- `Opportunity`
+- `Organization`
+- `PageCitability`
+- `PageIntent`
+- `Project`
+- `Report`
+- `ScrapeJob`
+- `ScrapeUrl`
+- `SentimentGuideline`
+- `SentimentTopic`
+- `Site`
+- `SiteCandidate`
+- `SiteEnrollment`
+- `SiteTopForm`
+- `SiteTopPage`
+- `Suggestion`
+- `TrialUser`
+- `TrialUserActivity`
+
+## V3 Behavior Notes
+
+- `Configuration` remains S3-backed in v3.
+- `KeyEvent` is deprecated in v3 and intentionally throws on access/mutation methods.
+- `LatestAudit` is virtual in v3 and derived from `Audit` queries (no dedicated table required).
+
+## Migrating from V2
+
+If you are upgrading from DynamoDB/ElectroDB-based v2:
+
+### What stays the same
+
+- You still use `createDataAccess(...)`.
+- You still access collections through `dataAccess.<Entity>` (for example `dataAccess.Site`).
+- Model/collection APIs are intended to stay stable for service callers.
+
+### What changes
+
+- Backing store is now Postgres via PostgREST, not DynamoDB/ElectroDB.
+- You must provide `postgrestUrl` (or `POSTGREST_URL` via wrapper env).
+- `Configuration` remains S3-backed (requires `s3Bucket`/`S3_CONFIG_BUCKET` when used).
+- `KeyEvent` is deprecated in v3 and now throws.
+- `LatestAudit` is no longer a dedicated table and is computed from `Audit` queries.
+
+### Required environment/config updates
+
+- Replace old Dynamo-specific configuration with:
+  - `POSTGREST_URL`
+  - optional `POSTGREST_SCHEMA`
+  - optional `POSTGREST_API_KEY`
+- Keep S3 config envs only if using `Configuration`:
+  - `S3_CONFIG_BUCKET`
+  - `AWS_REGION`
+
+## Development
+
+## Local Development
+
+### First-time setup
+
+From the monorepo root:
 
 ```bash
-npm run test:it
+npm install
 ```
 
-These tests create the schema, generate sample data, and test the data access patterns against the local DynamoDB instance.
+Optional: verify package tooling from this workspace:
 
-## Data Access API
+```bash
+cd packages/spacecat-shared-data-access
+node -v
+npm -v
+```
 
-The module provides the following DAOs:
+### Day-to-day workflow
 
-### Site Functions
-- `getSites`
-- `getSitesToAudit`
-- `getSitesWithLatestAudit`
-- `getSiteByBaseURL`
-- `getSiteByBaseURLWithAuditInfo`
-- `getSiteByBaseURLWithAudits`
-- `getSiteByBaseURLWithLatestAudit`
-- `addSite`
-- `updateSite`
-- `removeSite`
-- `findByPreviewURL`
-- `findByExternalOwnerIdAndExternalSiteId`
+1. Create/switch to a feature branch.
+2. Make code changes in `src/` and tests in `test/unit` and `test/it`.
+3. Run unit tests while iterating.
+4. Run integration tests before opening/merging a PR.
+5. Run lint and fix issues.
 
-### Site Candidate Functions
-- `getSiteCandidateByBaseURL`
-- `upsertSiteCandidate`
-- `siteCandidateExists`
-- `updateSiteCandidate`
+### Common commands (from `packages/spacecat-shared-data-access`)
 
-### Audit Functions
-- `getAuditsForSite`
-- `getAuditForSite`
-- `getLatestAudits`
-- `getLatestAuditForSite`
-- `addAudit`
+### Run unit tests
 
-### Site Top Pages Functions
-- `getTopPagesForSite`
-- `addSiteTopPage`
+```bash
+npm test
+```
 
-### FixEntity Functions
-- `getSuggestionsByFixEntityId` - Gets all suggestions associated with a specific FixEntity
-- `setSuggestionsForFixEntity` - Sets suggestions for a FixEntity by managing junction table relationships
+### Run unit tests with debugger
 
-### Suggestion Functions
-- `bulkUpdateStatus` - Updates the status of multiple suggestions in bulk
-- `getFixEntitiesBySuggestionId` - Gets all FixEntities associated with a specific Suggestion
+```bash
+npm run test:debug
+```
 
-### FixEntitySuggestion Functions
-- `allBySuggestionId` - Gets all junction records associated with a specific Suggestion
-- `allByFixEntityId` - Gets all junction records associated with a specific FixEntity
+### Run integration tests
 
-## Integrating Data Access in AWS Lambda Functions
+```bash
+npm run test:it
+```
 
-Our `spacecat-shared-data-access` module includes a wrapper that can be easily integrated into AWS Lambda functions using `@adobe/helix-shared-wrap`.
-This integration allows your Lambda functions to access and manipulate data.
+### Run lint
 
-### Steps for Integration
+```bash
+npm run lint
+```
 
-1. **Import the Data Access Wrapper**
+### Auto-fix lint issues
 
-   Along with other wrappers and utilities, import the `dataAccessWrapper`.
+```bash
+npm run lint:fix
+```
 
-   ```javascript
-   import dataAccessWrapper from '@adobe/spacecat-shared-data-access';
-   ```
+### Clean local install artifacts
 
-2. **Provide Required Environment Variables**
+```bash
+npm run clean
+```
 
-   The `dataAccessWrapper` requires the `DYNAMO_TABLE_NAME_DATA` environment variable to be set via AWS
-   secret assigned to your Lambda function.
+The integration suite under `test/it` is PostgREST-based and runs via Docker.
 
-   ```javascript
-   const { DYNAMO_TABLE_NAME_DATA } = context.env;
-   ```
+## Integration Tests
 
-3. **Modify Your Lambda Wrapper Script**
+Integration tests run a local Postgres + PostgREST stack via Docker Compose and execute
+the mocha suite under `test/it`.
 
-   Include `dataAccessWrapper` in the chain of wrappers when defining your Lambda handler.
+### Prerequisites
 
-   ```javascript
-   export const main = wrap(run)
-     .with(sqsEventAdapter)
-     .with(dataAccessWrapper) // Add this line
-     .with(sqs)
-     .with(secrets)
-     .with(helixStatus);
-   ```
+- Docker Desktop (or equivalent Docker daemon)
+- AWS CLI configured with credentials that can access the Spacecat Development AWS account
+  ECR repository (only needed when pulling the default private ECR image)
 
-4. **Access Data in Your Lambda Function**
+### Default image used by IT harness
 
-   Use the `dataAccess` object from the context to interact with your data layer.
+- Repository: `682033462621.dkr.ecr.us-east-1.amazonaws.com/mysticat-data-service`
+- Tag: `v1.11.0` (override via env var)
 
-   ```javascript
-   async function run(message, context) {
-     const { dataAccess } = context;
-     
-     // Example: Retrieve all sites
-     const sites = await dataAccess.Site.getSites();
-     // ... more logic ...
-   }
-   ```
+### Authenticate Docker to ECR
 
-### Example
+The default image is in a private ECR repo in:
+- **SpaceCat Development (AWS3338)**
 
-Here's a complete example of a Lambda function utilizing the data access wrapper:
+If you are setting this up for the first time:
+1. Get AWS credentials for **SpaceCat Development (AWS3338)** from `klam.corp.adobe.com`.
+2. Add them to `~/.aws/credentials` under a profile name you choose.
+3. Use that profile in the ECR login command.
 
-```javascript
-import wrap from '@adobe/helix-shared-wrap';
-import dataAccessWrapper from '@adobe/spacecat-shared-data-access';
-import sqsEventAdapter from './sqsEventAdapter';
-import sqs from './sqs';
-import secrets from '@adobe/helix-shared-secrets';
-import helixStatus from '@adobe/helix-status';
+Example `~/.aws/credentials` entry:
 
-async function run(message, context) {
-  const { dataAccess } = context;
-  try {
-    const sites = await dataAccess.Site.getSites();
-    // Function logic here
-  } catch (error) {
-    // Error handling
-  }
-}
+```ini
+[spacecat-dev]
+aws_access_key_id = <your-access-key-id>
+aws_secret_access_key = <your-secret-access-key>
+```
 
-export const main = wrap(run)
-  .with(sqsEventAdapter)
-  .with(dataAccessWrapper)
-  .with(sqs)
-  .with(secrets)
-  .with(helixStatus);
+Repository:
+
+- `682033462621.dkr.ecr.us-east-1.amazonaws.com/mysticat-data-service`
+
+Then authenticate Docker to ECR:
+
+```bash
+aws ecr get-login-password --profile spacecat-dev --region us-east-1 \
+  | docker login --username AWS --password-stdin 682033462621.dkr.ecr.us-east-1.amazonaws.com
 ```
 
-## Contributing
+### Run
 
-Contributions to `spacecat-shared-data-access` are welcome. Please adhere to the standard Git workflow and submit pull requests for proposed changes.
+```bash
+npm run test:it
+```
 
-## Local Development and Testing
+### Useful overrides
 
-### Testing with Dependent Projects Before Merging
+- `MYSTICAT_DATA_SERVICE_TAG`: override image tag (recommended for version bumps)
+- `MYSTICAT_DATA_SERVICE_REPOSITORY`: override image repository
+- `MYSTICAT_DATA_SERVICE_PLATFORM`: override container platform (default `linux/amd64`)
+- `IT_POSTGREST_PORT`: override exposed PostgREST port (default `3300`)
+- `IT_POSTGRES_PORT`: override exposed Postgres port (default `55432`)
 
-When making changes to this package, you can test them in dependent projects (like `spacecat-api-service`) before merging using the following approach:
+```bash
+export MYSTICAT_DATA_SERVICE_TAG=v1.11.0
+export MYSTICAT_DATA_SERVICE_PLATFORM=linux/amd64
+# optional if repository changes
+export MYSTICAT_DATA_SERVICE_REPOSITORY=682033462621.dkr.ecr.us-east-1.amazonaws.com/mysticat-data-service
+```
 
-1. Commit and push your changes to a branch in this repository
-2. Get the commit ID of your push
-3. In your dependent project, temporarily modify the package.json dependency:
+## TypeScript
 
-   ```json
-   // From:
-   "@adobe/spacecat-shared-data-access": "2.13.1",
-   
-   // To:
-   "@adobe/spacecat-shared-data-access": "https://gitpkg.now.sh/adobe/spacecat-shared/packages/spacecat-shared-data-access?YOUR_COMMIT_ID",
-   ```
+Type definitions are shipped from:
+- `src/index.d.ts`
+- `src/models/**/index.d.ts`
 
-4. Run `npm install` in your dependent project
-5. Test your changes
-6. Once testing is complete and your PR is merged, update the dependent project to use the released version
+Use the package directly in TS projects; no extra setup required.
 
 ## License
 
-Licensed under the Apache-2.0 License.
+Apache-2.0

package/docker-compose.test.yml

@@ -0,0 +1,39 @@
+# Docker Compose for integration testing — PostgreSQL + PostgREST
+name: spacecat-data-access-test
+
+services:
+  db:
+    image: postgres:16-alpine
+    container_name: spacecat-test-db
+    environment:
+      POSTGRES_USER: postgres
+      POSTGRES_PASSWORD: postgres
+      POSTGRES_DB: spacecat_test
+    ports:
+      - "54320:5432"
+    tmpfs:
+      - /var/lib/postgresql/data
+    volumes:
+      - ./test/it/v3/init-db.sql:/docker-entrypoint-initdb.d/01-init.sql:ro
+    healthcheck:
+      test: ["CMD-SHELL", "pg_isready -U postgres"]
+      interval: 2s
+      timeout: 3s
+      retries: 10
+
+  postgrest:
+    image: postgrest/postgrest:v14.4
+    container_name: spacecat-test-postgrest
+    depends_on:
+      db:
+        condition: service_healthy
+    environment:
+      PGRST_DB_URI: postgres://postgrest_authenticator:postgrest@db:5432/spacecat_test
+      PGRST_DB_SCHEMAS: public
+      PGRST_DB_ANON_ROLE: postgrest_anon
+      PGRST_DB_EXTRA_SEARCH_PATH: ""
+      PGRST_LOG_LEVEL: warn
+      PGRST_ADMIN_SERVER_PORT: 3001
+    ports:
+      - "3456:3000"
+      - "3457:3001"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adobe/spacecat-shared-data-access",
-  "version": "2.109.0",
+  "version": "3.0.0",
   "description": "Shared modules of the Spacecat Services - Data Access",
   "type": "module",
   "engines": {
@@ -10,7 +10,9 @@
   "main": "src/index.js",
   "types": "src/index.d.ts",
   "scripts": {
-    "test:it": "mocha --require ./test/it/fixtures.js --spec \"test/it/**/*.test.js\"",
+    "test:it": "npm run test:it:legacy && npm run test:it:postgrest",
+    "test:it:legacy": "IT_SEED_MODE=none mocha --require ./test/it/fixtures.js --spec \"test/it/**/*.test.js\" --ignore \"test/it/postgrest/**/*.test.js\"",
+    "test:it:postgrest": "IT_SEED_MODE=tenant-sql mocha --require ./test/it/fixtures.js --spec \"test/it/postgrest/**/*.test.js\"",
     "test": "c8 mocha --spec \"test/unit/**/*.test.js\"",
     "test:debug": "mocha --inspect-brk --require ./test/setup-env.js --spec \"test/unit/**/*.test.js\"",
     "test:debug:config": "mocha --inspect-brk --require ./test/setup-env.js --spec \"test/unit/models/site/config.test.js\"",
@@ -39,19 +41,16 @@
   },
   "dependencies": {
     "@adobe/spacecat-shared-utils": "1.81.1",
-    "@aws-sdk/client-dynamodb": "3.940.0",
+    "@supabase/postgrest-js": "^1.21.4",
     "@aws-sdk/client-s3": "^3.940.0",
-    "@aws-sdk/lib-dynamodb": "3.940.0",
     "@types/joi": "17.2.3",
     "aws-xray-sdk": "3.12.0",
-    "electrodb": "3.5.0",
     "joi": "18.0.2",
     "pluralize": "8.0.0"
   },
   "devDependencies": {
     "chai": "6.2.1",
     "chai-as-promised": "8.0.2",
-    "dynamo-db-local": "9.6.0",
     "nock": "14.0.10",
     "sinon": "21.0.0",
     "sinon-chai": "4.0.1"