From ce79d4378cee9dbde634c964d6e0950270fbb895 Mon Sep 17 00:00:00 2001
From: Ytbarek Hailu <ytbarek.hailu@snowflake.com>
Date: Fri, 27 Feb 2026 13:32:08 -0800
Subject: [PATCH 1/5] Added plan command

---
 CHANGELOG.md                                  |   4 +
 CONTRIBUTING.md                               | 117 ++++++++++++++++++
 README.md                                     |  69 +++++++++--
 .../com/snowflake/dlsync/ChangeManager.java   |  65 +++++++++-
 src/main/java/com/snowflake/dlsync/Main.java  |   6 +-
 .../snowflake/dlsync/models/ChangeType.java   |   2 +-
 .../snowflake/dlsync/ChangeManagerTest.java   |  38 ++++++
 .../java/com/snowflake/dlsync/MainTest.java   |  15 +++
 8 files changed, 305 insertions(+), 11 deletions(-)
 create mode 100644 CONTRIBUTING.md

diff --git a/CHANGELOG.md b/CHANGELOG.md
index a96fd5c..a616be0 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,6 +1,10 @@
 # DLSync Changelog
 
 This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [3.2.0] - 2026-02-27
+### Added
+- Added PLAN command for deployment preview (dry-run without database modifications)
 ## [3.1.0] - 2026-02-10
 ### Added
 - Added support for AGENTS object type
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..e8279a6
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,117 @@
+# Contributing to DLSync
+
+Thank you for your interest in contributing to DLSync! We welcome contributions from the community.
+
+## Prerequisites
+
+- Java 11 or higher
+- Gradle 7.0 or higher
+- Git
+- Snowflake account (for testing changes)
+
+## Quick Start
+
+### 1. Fork the Repository
+
+1. Click **Fork** on the [DLSync GitHub repository](https://github.com/Snowflake-Labs/dlsync)
+2. This creates a copy under your GitHub account
+
+### 2. Clone Your Fork
+
+```bash
+git clone https://github.com/YOUR_USERNAME/dlsync.git
+cd dlsync
+```
+
+### 3. Add Upstream Remote
+
+```bash
+git remote add upstream https://github.com/Snowflake-Labs/dlsync.git
+```
+
+---
+
+## Making Changes
+
+### 1. Create a Feature Branch
+
+```bash
+# Update your local main branch
+git fetch upstream
+git checkout main
+git rebase upstream/main
+
+# Create a new branch for your changes
+git checkout -b feature/your-feature-name
+```
+
+### 2. Make Your Changes
+
+- Edit the necessary files
+- Keep changes focused and concise
+- Follow the existing code style
+
+### 3. Test Your Changes
+
+```bash
+# Run tests
+./gradlew test
+
+# Build the project
+./gradlew build
+```
+
+### 4. Update Documentation
+
+- Update `README.md` if user-facing changes
+- add changelog to `CHANGELOG.md`
+
+### 5. Commit Your Changes
+
+```bash
+git add .
+git commit -m "Description of your changes"
+```
+
+---
+
+## Creating a Pull Request
+
+### 1. Push Your Branch
+
+```bash
+git push origin feature/your-feature-name
+```
+
+### 2. Create Pull Request on GitHub
+
+1. Go to your forked repository on GitHub: `https://github.com/YOUR_USERNAME/dlsync`
+2. You should see a notification: "Your branch is ahead of Snowflake-Labs:main"
+3. Click the **Compare & pull request** button (or go to **Pull Requests** tab → **New Pull Request**)
+4. Verify the pull request details:
+   - **Base repository**: `Snowflake-Labs/dlsync`
+   - **Base branch**: `main`
+   - **Head repository**: `YOUR_USERNAME/dlsync`
+   - **Compare branch**: `feature/your-feature-name`
+5. Add a title and description:
+   ```
+   Title: [FEATURE|FIX|DOCS] Brief description of changes
+   
+   Description:
+   - What changes are included
+   - Why this change is needed
+   - Any related issues (e.g., Closes #123)
+   ```
+6. Click **Create Pull Request**
+
+### 4. Review Process
+
+- A maintainer will review your PR
+- CI/CD checks must pass
+- Address any feedback or changes requested
+- Once approved, your PR will be merged!
+
+---
+
+Thank you for contributing! 🙏
+
diff --git a/README.md b/README.md
index 6d56c00..d6d0a32 100644
--- a/README.md
+++ b/README.md
@@ -28,6 +28,7 @@ DLSync also understands interdependencies between different scripts, thus applyi
    1. [How to use this tool](#how-to-use-this-tool)
       1. [Deploy](#deploy)
       1. [Test](#test)
+      1. [Plan](#plan)
       1. [Rollback](#rollback)
       1. [Verify](#verify)
       1. [Create script](#create-script)
@@ -41,6 +42,7 @@ DLSync also understands interdependencies between different scripts, thus applyi
    1. [dl_sync_change_sync](#dl_sync_change_sync)
    1. [dl_sync_script_event](#dl_sync_script_event)
 1. [Example scripts](#example-scripts)
+1. [Contributing](#contributing)
 
 ## Key Features 
 - Hybrid Change Management: It combines declarative and migration based change management to manage database changes
@@ -230,9 +232,9 @@ Writing unit tests follows a 3-step process:
 - Add the query to refer to the database object with a select statement.
 For example, if you have a view named `SAMPLE_VIEW`  with the following content:
 ```
-create or replace view ${MY_DB}.{MY_SCHEMA}.SAMPLE_VIEW as 
-select tb1.id, tb1.my_column || '->' || tb2.my_column as my_new_column from ${MY_DB}.{MY_SECOND_SCHEMA}.MY_TABLE_1 tb_1
-join ${MY_DB}.{MY_SECOND_SCHEMA}.MY_TABLE_2 tb2 
+create or replace view ${MY_DB}.${MY_SCHEMA}.SAMPLE_VIEW as 
+select tb1.id, tb1.my_column || '->' || tb2.my_column as my_new_column from ${MY_DB}.${MY_SECOND_SCHEMA}.MY_TABLE_1 tb_1
+join ${MY_DB}.${MY_SECOND_SCHEMA}.MY_TABLE_2 tb2 
     on tb1.id = tb2.id;
 ```
 
@@ -250,7 +252,7 @@ MY_TABLE_2 as (
 expected_data as (
     select '1' as id, 'old_value1->new_value1' as my_new_column
 )
-select * from ${MY_DB}.{MY_SCHEMA}.SAMPLE_VIEW;
+select * from ${MY_DB}.${MY_SCHEMA}.SAMPLE_VIEW;
 ```
 Then dlsync will generate a query with the following content to validate the test:
 ```
@@ -267,8 +269,8 @@ expected_data as (
     select '1' as id, 'old_value1->new_value1' as my_new_column
 ),
 ACTUAL_DATA as (
-select tb1.id, tb1.my_column || '->' || tb2.my_column as my_new_column from ${MY_DB}.{MY_SECOND_SCHEMA}.MY_TABLE_1 tb_1
-join ${MY_DB}.{MY_SECOND_SCHEMA}.MY_TABLE_2 tb2 
+select tb1.id, tb1.my_column || '->' || tb2.my_column as my_new_column from ${MY_DB}.${MY_SECOND_SCHEMA}.MY_TABLE_1 tb_1
+join ${MY_DB}.${MY_SECOND_SCHEMA}.MY_TABLE_2 tb2 
     on tb1.id = tb2.id
 ),
 assertion as (
@@ -408,6 +410,53 @@ The test module can be triggered using the following command:
 dlsync test -s path/to/db_scripts -p dev
 ```
 
+#### Plan
+This module is used to preview changes before deploying them to the database. It shows what changes would be made without actually executing them, allowing you to review and understand the impact before committing to the deployment.
+The plan command performs a dry-run analysis that:
+- Identifies which scripts have changed since the last deployment
+- Shows the dependency order in which changes would be applied
+- Displays the complete content of all scripts that would be executed
+- Provides metadata about each script (type, version, author, hash)
+- **Does NOT modify the database in any way** (read-only operation)
+
+The plan module can be triggered using the following command:
+```
+dlsync plan -s path/to/db_scripts -p dev
+```
+
+**Output Example:**
+```
+========== DEPLOYMENT PLAN ==========
+Total changes to deploy: 2
+========== DEPLOYMENT ORDER ==========
+1 of 2: MY_DB.MY_SCHEMA.SAMPLE_TABLE
+   Type: Migration
+   Object: MY_DB.MY_SCHEMA.SAMPLE_TABLE (Version: 1)
+   Author: john.doe@company.com
+   Hash: a1b2c3d4e5f6g7h8
+   Content:
+   CREATE TABLE MY_DB.MY_SCHEMA.SAMPLE_TABLE(id VARCHAR, my_column VARCHAR);
+========== END CONTENT ==========
+2 of 2: MY_DB.MY_SCHEMA.SAMPLE_VIEW
+   Type: Declarative
+   Object: MY_DB.MY_SCHEMA.SAMPLE_VIEW
+   Object Type: VIEW
+   Hash: b2c3d4e5f6g7h8i9
+   Content:
+   CREATE VIEW MY_DB.MY_SCHEMA.SAMPLE_VIEW AS SELECT * FROM MY_DB.MY_SCHEMA.SAMPLE_TABLE;
+========== END CONTENT ==========
+========== END PLAN ==========
+```
+
+**Use Cases:**
+- Review changes before deployment in development/staging environments
+- Audit what will be deployed to production
+- Integrate with CI/CD pipelines as a pre-deployment validation step
+- Generate deployment plans for approval workflows
+- Verify script dependencies are correct before execution
+
+**Note:** The plan command is read-only and safe to run multiple times without side effects. However, it will create the necessary DLSync metadata tables if they don't already exist in the target schema.
+
 #### Rollback
 This module is used to rollback changes to the previous deployment. It will rollback the changes to the database objects based on the script files. This should be triggered after you have rolled back the git repository of the script files. 
 The rollback works first by identifying the changes between the current deployment and the previous deployment. For declarative scripts (views, udf, stored procedures and file formats) it will replace them with the current script(i.e previous version as you have already made git rollback). 
@@ -471,7 +520,7 @@ For managing account-level objects, the role must have:
 ## DLSync Metadata Tables
 DLSync stores script metadata, deployment history, and logs in the database.
 DLSync will depend on these tables to track the changes and deployment history. If these tables are missing from the schema and database provided in the connection parameter, then DLSync will create these tables. 
-Please make sure the role provided in the connection has the necessary privileges to create tables in the schema. 
+Please make sure the role provided in the connection has the necessary privileges to create tables in the schema.
 
 **_N.B: Since DLSync uses these tables to track the changes, it is recommended not to delete or change these tables. It is also important not to change the schema of the connection. If DLSync is not able to find these tables in the schema, it will create them and assume it is running for the first time._**
 
@@ -517,3 +566,9 @@ created_ts: the timestamp when was this change added
 ```
 ## Example scripts
 To explore the tool, you can use the example scripts provided in the `example_scripts` directory.
+
+## Contributing
+
+We welcome contributions from the community! Whether you're fixing bugs, adding features, or improving documentation, your help is appreciated.
+
+Please see [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines on how to contribute to this project.
\ No newline at end of file
diff --git a/src/main/java/com/snowflake/dlsync/ChangeManager.java b/src/main/java/com/snowflake/dlsync/ChangeManager.java
index 33a7284..6f04e89 100644
--- a/src/main/java/com/snowflake/dlsync/ChangeManager.java
+++ b/src/main/java/com/snowflake/dlsync/ChangeManager.java
@@ -86,6 +86,69 @@ public void deploy(boolean onlyHashes) throws SQLException, IOException, NoSuchA
         }
     }
 
+    public void plan()  throws SQLException, IOException, NoSuchAlgorithmException {
+        log.info("Started PLAN command for deployment");
+
+        try {
+            scriptRepo.loadScriptHash();
+
+            // Get all changed scripts (same logic as deploy)
+            List<Script> changedScripts = scriptSource.getAllScripts()
+                    .stream()
+                    .filter(script -> !config.isScriptExcluded(script))
+                    .filter(script -> scriptRepo.isScriptChanged(script))
+                    .collect(Collectors.toList());
+            dependencyGraph.addNodes(changedScripts);
+            List<Script> sequencedScripts = dependencyGraph.topologicalSort();
+
+            // Show deployment summary
+            System.out.println("========== DEPLOYMENT PLAN ==========");
+            System.out.println("Total changes to deploy: " + changedScripts.size());
+            System.out.println("========== DEPLOYMENT ORDER ==========");
+
+            if (changedScripts.isEmpty()) {
+                System.out.println("PLAN: No changes to deploy");
+                System.out.println("========== END PLAN ==========");
+                return;
+            }
+
+            int index = 1;
+            for (Script script : sequencedScripts) {
+                parameterInjector.injectParameters(script);
+                validateScript(script);
+                System.out.println(index + " of " + sequencedScripts.size() + ": " + script);
+
+                if (script instanceof MigrationScript) {
+                    MigrationScript migration = (MigrationScript) script;
+                    System.out.println("   Type: Migration");
+                    System.out.println("   Object: " + migration.getFullObjectName() + " (Version: " + migration.getVersion() + ")");
+                    System.out.println("   Author: " + (migration.getAuthor() != null ? migration.getAuthor() : "N/A"));
+                    System.out.println("   Hash: " + script.getHash());
+                } else {
+                    System.out.println("   Type: Declarative");
+                    System.out.println("   Object: " + script.getFullObjectName());
+                    System.out.println("   Object Type: " + script.getObjectType());
+                    System.out.println("   Hash: " + script.getHash());
+                }
+
+                // Show full SQL content without truncation
+                System.out.println("   Content:");
+                System.out.println(script.getContent());
+                System.out.println("========== END CONTENT ==========");
+
+                index++;
+            }
+
+            System.out.println("========== END PLAN ==========");
+
+        } catch (Exception e) {
+            System.err.println("ERROR: Plan command failed: " + e.getMessage());
+            log.error("Plan command failed: {}", e.getMessage());
+            System.out.println("========== END PLAN ==========");
+            throw e;
+        }
+    }
+
     public void rollback() throws SQLException, IOException {
         log.info("Starting ROLLBACK scripts.");
         startSync(ChangeType.ROLLBACK);
@@ -282,7 +345,5 @@ public void endSyncError(ChangeType changeType, String message) throws SQLExcept
     public void endSyncSuccess(ChangeType changeType, Long changeCount) throws SQLException {
         scriptRepo.updateChangeSync(changeType, Status.SUCCESS, "Successfully completed " + changeType.toString() , changeCount);
     }
-
-
 }
 
diff --git a/src/main/java/com/snowflake/dlsync/Main.java b/src/main/java/com/snowflake/dlsync/Main.java
index b2aba62..caf7c7b 100644
--- a/src/main/java/com/snowflake/dlsync/Main.java
+++ b/src/main/java/com/snowflake/dlsync/Main.java
@@ -56,6 +56,10 @@ public static void main(String[] args) throws SQLException {
                     changeManager.test();
                     log.info("DLsync successfully tested.");
                     break;
+                case PLAN:
+                    changeManager.plan();
+                    log.info("DLSync plan completed successfully.");
+                    break;
                 default:
                     log.error("Change type not specified as an argument.");
             }
@@ -103,7 +107,7 @@ public static CommandLine buildCommandOptions(String[] args) throws ParseExcepti
             CommandLine commandLine = new DefaultParser().parse(options, argsWithoutCommand);
             return commandLine;
         } catch (ParseException e) {
-            new HelpFormatter().printHelp("dlsync [deploy|rollback|verify|create-script|create-lineage] [options]", "options:", options, "");
+            new HelpFormatter().printHelp("dlsync [deploy|rollback|verify|create-script|create-lineage|test|plan] [options]", "options:", options, "");
             throw e;
         }
 
diff --git a/src/main/java/com/snowflake/dlsync/models/ChangeType.java b/src/main/java/com/snowflake/dlsync/models/ChangeType.java
index 9e200d9..8c08320 100644
--- a/src/main/java/com/snowflake/dlsync/models/ChangeType.java
+++ b/src/main/java/com/snowflake/dlsync/models/ChangeType.java
@@ -1,5 +1,5 @@
 package com.snowflake.dlsync.models;
 
 public enum ChangeType {
-    DEPLOY, VERIFY, ROLLBACK, CREATE_SCRIPT, CREATE_LINEAGE, TEST
+    DEPLOY, VERIFY, ROLLBACK, CREATE_SCRIPT, CREATE_LINEAGE, TEST, PLAN
 };
diff --git a/src/test/java/com/snowflake/dlsync/ChangeManagerTest.java b/src/test/java/com/snowflake/dlsync/ChangeManagerTest.java
index b17dbb7..af5ccc5 100644
--- a/src/test/java/com/snowflake/dlsync/ChangeManagerTest.java
+++ b/src/test/java/com/snowflake/dlsync/ChangeManagerTest.java
@@ -422,5 +422,43 @@ void testRollbackWithDeploymentChanges() throws SQLException, IOException {
 
         verify(mockScriptRepo, times(1)).createScriptObject(any(), eq(false));
     }
+
+    @Test
+    @DisplayName("Plan command should NOT make any database changes")
+    void testPlanCommandMakesNoDatabaseChanges() throws SQLException, IOException, NoSuchAlgorithmException {
+        // Setup: Create test scripts with changes
+        SchemaScript tableScript = ScriptFactory.getSchemaScript(
+            "TEST_DB", "TEST_SCHEMA", ScriptObjectType.TABLES,
+            "MY_TABLE", "CREATE TABLE MY_TABLE(id INT);"
+        );
+
+        SchemaScript viewScript = ScriptFactory.getSchemaScript(
+            "TEST_DB", "TEST_SCHEMA", ScriptObjectType.VIEWS,
+            "MY_VIEW", "CREATE VIEW MY_VIEW AS SELECT * FROM MY_TABLE;"
+        );
+
+        List<Script> allScripts = Arrays.asList(tableScript, viewScript);
+
+        // Mock the behavior
+        when(mockConfig.isScriptExcluded(any())).thenReturn(false);
+        when(mockScriptSource.getAllScripts()).thenReturn(allScripts);
+        when(mockScriptRepo.isScriptChanged(any())).thenReturn(true);
+
+        List<Script> orderedScripts = Arrays.asList(tableScript, viewScript);
+        when(mockDependencyGraph.topologicalSort()).thenReturn(orderedScripts);
+
+        // Execute plan command
+        changeManager.plan();
+
+        // Assert: Verify NO database modifications were made
+        verify(mockScriptRepo, never()).createScriptObject(any(), anyBoolean());
+        verify(mockScriptRepo, never()).insertChangeSync(any(), any(), anyString());
+        verify(mockScriptRepo, never()).updateChangeSync(any(), any(), anyString(), any());
+        verify(mockScriptRepo, never()).executeRollback(any());
+
+        // Verify that only read-only operations were called
+        verify(mockScriptRepo, times(1)).loadScriptHash();
+        verify(mockParameterInjector, times(2)).injectParameters(isA(Script.class));
+    }
 }
 
diff --git a/src/test/java/com/snowflake/dlsync/MainTest.java b/src/test/java/com/snowflake/dlsync/MainTest.java
index a2ddcee..cad8979 100644
--- a/src/test/java/com/snowflake/dlsync/MainTest.java
+++ b/src/test/java/com/snowflake/dlsync/MainTest.java
@@ -81,6 +81,21 @@ public void testGetChangeType() {
         assertTrue(changeType == ChangeType.DEPLOY);
     }
 
+    @Test
+    void testGetChangeTypeForPlan() {
+        String[] args = {"plan"};
+        ChangeType changeType = Main.getChangeType(args);
+        assertEquals(ChangeType.PLAN, changeType, "Should recognize 'plan' as PLAN command");
+
+        String[] args2 = {"PLAN"};
+        changeType = Main.getChangeType(args2);
+        assertEquals(ChangeType.PLAN, changeType, "Should recognize 'PLAN' (uppercase) as PLAN command");
+
+        String[] args3 = {"Plan"};
+        changeType = Main.getChangeType(args3);
+        assertEquals(ChangeType.PLAN, changeType, "Should recognize 'Plan' (mixed case) as PLAN command");
+    }
+
     @Test
     void testTargetSchema() throws ParseException {
         String[] args = {"create_script", "--target-schemas", "schema1,schema2"};

From 1152e33ad969e2f1fd31ada13c9f7dc470447da3 Mon Sep 17 00:00:00 2001
From: Christian van Rodijnen <christian.vanrodijnen@surf.nl>
Date: Sat, 28 Feb 2026 13:39:37 +0100
Subject: [PATCH 2/5] implementation tag

---
 .../main/example_db/MAIN_SCHEMA/TAG/COLUMN_CLASSIFICATION.sql | 4 ++++
 .../java/com/snowflake/dlsync/models/ScriptObjectType.java    | 3 ++-
 2 files changed, 6 insertions(+), 1 deletion(-)
 create mode 100644 example_scripts/main/example_db/MAIN_SCHEMA/TAG/COLUMN_CLASSIFICATION.sql

diff --git a/example_scripts/main/example_db/MAIN_SCHEMA/TAG/COLUMN_CLASSIFICATION.sql b/example_scripts/main/example_db/MAIN_SCHEMA/TAG/COLUMN_CLASSIFICATION.sql
new file mode 100644
index 0000000..d2a1254
--- /dev/null
+++ b/example_scripts/main/example_db/MAIN_SCHEMA/TAG/COLUMN_CLASSIFICATION.sql
@@ -0,0 +1,4 @@
+---version: 0, author: DlSync
+create or replace TAG ${EXAMPLE_DB}.${MAIN_SCHEMA}.COLUMN_CLASSIFICATION allowed_values 'PUBLIC', 'INTERNAL', 'RESTRICTED', 'SENSITIVE';
+---rollback: DROP TAG IF EXISTS ${EXAMPLE_DB}.${MAIN_SCHEMA}.COLUMN_CLASSIFICATION;
+---verify: SHOW TAGS LIKE 'COLUMN_CLASSIFICATION' IN ${EXAMPLE_DB}.${MAIN_SCHEMA};
\ No newline at end of file
diff --git a/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java b/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java
index 13f1b68..7a667d5 100644
--- a/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java
+++ b/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java
@@ -1,6 +1,6 @@
 package com.snowflake.dlsync.models;
 
-public enum ScriptObjectType {
+public enum ScriptObjectType {    
     VIEWS("VIEW", ObjectLevel.SCHEMA, false),
     FUNCTIONS("FUNCTION", ObjectLevel.SCHEMA, false),
     PROCEDURES("PROCEDURE", ObjectLevel.SCHEMA, false),
@@ -23,6 +23,7 @@ public enum ScriptObjectType {
     STORAGE_INTEGRATIONS("STORAGE INTEGRATION", ObjectLevel.ACCOUNT, false),
     WAREHOUSES("WAREHOUSE", ObjectLevel.ACCOUNT, false),
     NOTEBOOKS("NOTEBOOK", ObjectLevel.SCHEMA, false),
+    TAG("TAG", ObjectLevel.SCHEMA, false),
 
     // Migration-enabled objects
     TABLES("TABLE", ObjectLevel.SCHEMA, true),

From 3444612ea56a0168107c7241d3de242f213d273b Mon Sep 17 00:00:00 2001
From: Christian van Rodijnen <christian.vanrodijnen@surf.nl>
Date: Sat, 28 Feb 2026 13:44:10 +0100
Subject: [PATCH 3/5] Modification based on review

---
 src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java b/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java
index 7a667d5..7eb5c7d 100644
--- a/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java
+++ b/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java
@@ -23,7 +23,7 @@ public enum ScriptObjectType {
     STORAGE_INTEGRATIONS("STORAGE INTEGRATION", ObjectLevel.ACCOUNT, false),
     WAREHOUSES("WAREHOUSE", ObjectLevel.ACCOUNT, false),
     NOTEBOOKS("NOTEBOOK", ObjectLevel.SCHEMA, false),
-    TAG("TAG", ObjectLevel.SCHEMA, false),
+    TAGS("TAG", ObjectLevel.SCHEMA, false),
 
     // Migration-enabled objects
     TABLES("TABLE", ObjectLevel.SCHEMA, true),

From 79e81aeac7e7adc7305a3418ff21ba0e1ce9ef84 Mon Sep 17 00:00:00 2001
From: Christian van r <christianvanr@gmail.com>
Date: Fri, 6 Mar 2026 07:27:11 +0100
Subject: [PATCH 4/5] Modification after review, removed headers and make
 folder plural

---
 .../main/example_db/MAIN_SCHEMA/TAG/COLUMN_CLASSIFICATION.sql | 4 ----
 .../example_db/MAIN_SCHEMA/TAGS/COLUMN_CLASSIFICATION.sql     | 1 +
 2 files changed, 1 insertion(+), 4 deletions(-)
 delete mode 100644 example_scripts/main/example_db/MAIN_SCHEMA/TAG/COLUMN_CLASSIFICATION.sql
 create mode 100644 example_scripts/main/example_db/MAIN_SCHEMA/TAGS/COLUMN_CLASSIFICATION.sql

diff --git a/example_scripts/main/example_db/MAIN_SCHEMA/TAG/COLUMN_CLASSIFICATION.sql b/example_scripts/main/example_db/MAIN_SCHEMA/TAG/COLUMN_CLASSIFICATION.sql
deleted file mode 100644
index d2a1254..0000000
--- a/example_scripts/main/example_db/MAIN_SCHEMA/TAG/COLUMN_CLASSIFICATION.sql
+++ /dev/null
@@ -1,4 +0,0 @@
----version: 0, author: DlSync
-create or replace TAG ${EXAMPLE_DB}.${MAIN_SCHEMA}.COLUMN_CLASSIFICATION allowed_values 'PUBLIC', 'INTERNAL', 'RESTRICTED', 'SENSITIVE';
----rollback: DROP TAG IF EXISTS ${EXAMPLE_DB}.${MAIN_SCHEMA}.COLUMN_CLASSIFICATION;
----verify: SHOW TAGS LIKE 'COLUMN_CLASSIFICATION' IN ${EXAMPLE_DB}.${MAIN_SCHEMA};
\ No newline at end of file
diff --git a/example_scripts/main/example_db/MAIN_SCHEMA/TAGS/COLUMN_CLASSIFICATION.sql b/example_scripts/main/example_db/MAIN_SCHEMA/TAGS/COLUMN_CLASSIFICATION.sql
new file mode 100644
index 0000000..029158e
--- /dev/null
+++ b/example_scripts/main/example_db/MAIN_SCHEMA/TAGS/COLUMN_CLASSIFICATION.sql
@@ -0,0 +1 @@
+create or replace TAG ${EXAMPLE_DB}.${MAIN_SCHEMA}.COLUMN_CLASSIFICATION allowed_values 'PUBLIC', 'INTERNAL', 'RESTRICTED', 'SENSITIVE';

From 739400aabb871962240dce9eca3ac5ce57f3af98 Mon Sep 17 00:00:00 2001
From: Ytbarek Hailu <ytbarek.hailu@snowflake.com>
Date: Mon, 9 Mar 2026 08:46:39 -0700
Subject: [PATCH 5/5] Added Row access policy object

---
 CHANGELOG.md                                  |  2 ++
 README.md                                     |  8 ++---
 .../ROW_ACCESS_POLICIES/CUSTOMER_ACCESS.SQL   |  9 +++++
 .../dlsync/models/ScriptObjectType.java       |  1 +
 .../dlsync/parser/SqlTokenizerTest.java       | 34 +++++++++++++++++++
 5 files changed, 50 insertions(+), 4 deletions(-)
 create mode 100644 example_scripts/main/example_db/MAIN_SCHEMA/ROW_ACCESS_POLICIES/CUSTOMER_ACCESS.SQL

diff --git a/CHANGELOG.md b/CHANGELOG.md
index a616be0..931fd79 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -5,6 +5,8 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 ## [3.2.0] - 2026-02-27
 ### Added
 - Added PLAN command for deployment preview (dry-run without database modifications)
+- Added support for TAGS object type
+- Added support for ROW_ACCESS_POLICIES object type
 ## [3.1.0] - 2026-02-10
 ### Added
 - Added support for AGENTS object type
diff --git a/README.md b/README.md
index d6d0a32..9034832 100644
--- a/README.md
+++ b/README.md
@@ -115,7 +115,7 @@ Where
   - Other account-level objects (users, resource monitors, integrations, etc.)
 - **database_name_*:** is the database name of your project, 
 - **schema_name_*:** are schemas inside the database, 
-- **object_type:** is type of the object only 1 of the following (VIEWS, FUNCTIONS, PROCEDURES, FILE_FORMATS, TABLES, SEQUENCES, STAGES, STREAMS, TASKS, STREAMLITS, PIPES, ALERTS, DYNAMIC_TABLES, MASKING_POLICIES, NOTEBOOKS, CORTEX_SEARCH_SERVICES, SEMANTIC_VIEWS, AGENTS),
+- **object_type:** is type of the object only 1 of the following (VIEWS, FUNCTIONS, PROCEDURES, FILE_FORMATS, TABLES, SEQUENCES, STAGES, STREAMS, TASKS, STREAMLITS, PIPES, ALERTS, DYNAMIC_TABLES, MASKING_POLICIES, ROW_ACCESS_POLICIES, TAGS, NOTEBOOKS, CORTEX_SEARCH_SERVICES, SEMANTIC_VIEWS, AGENTS),
 - **object_name_*.sql:** are individual database object scripts.
 - **config.yml:** is a configuration file used to configure DLSync behavior.
 - **parameter-[profile-*].properties:** is parameter to value map file. This is going to be used by corresponding individual instances of your database.
@@ -133,7 +133,7 @@ For example, if you have a view named `SAMPLE_VIEW` in schema `MY_SCHEMA` in dat
 
 The structure and content of the scripts differ based on the type of script. This tool categorizes scripts into 2 types: Declarative scripts and Migration scripts.
 #### 1. Declarative Script
-This type of script is used for object types of VIEWS, FUNCTIONS, PROCEDURES, FILE_FORMATS, PIPES, MASKING_POLICIES, NOTEBOOKS, CORTEX_SEARCH_SERVICES, SEMANTIC_VIEWS, AGENTS, STREAMLITS, RESOURCE_MONITORS, NETWORK_POLICIES, SESSION_POLICIES, PASSWORD_POLICIES, AUTHENTICATION_POLICIES, API_INTEGRATIONS, NOTIFICATION_INTEGRATIONS, SECURITY_INTEGRATIONS, STORAGE_INTEGRATIONS, and WAREHOUSES.
+This type of script is used for object types of VIEWS, FUNCTIONS, PROCEDURES, FILE_FORMATS, PIPES, MASKING_POLICIES, ROW_ACCESS_POLICIES, TAGS, NOTEBOOKS, CORTEX_SEARCH_SERVICES, SEMANTIC_VIEWS, AGENTS, STREAMLITS, RESOURCE_MONITORS, NETWORK_POLICIES, SESSION_POLICIES, PASSWORD_POLICIES, AUTHENTICATION_POLICIES, API_INTEGRATIONS, NOTIFICATION_INTEGRATIONS, SECURITY_INTEGRATIONS, STORAGE_INTEGRATIONS, and WAREHOUSES.
 In this type of script, you define the current state (desired state) of the object.
 When a change is made to the script, DLSync replaces the current object with the updated definition. 
 These types of scripts must always have a `create or replace` statement. Every time you make a change to the script, DLSync will replace the object with the new definition.
@@ -499,7 +499,7 @@ The role must have privileges to create and manage DLSync tracking tables in the
 > **Note:** the database and schema specified in the connection will be used to store the DLSync tracking tables.
 
 ### Database-Level Objects
-For managing database-level objects (VIEWS, FUNCTIONS, PROCEDURES, TABLES, SEQUENCES, STAGES, STREAMS, TASKS, ALERTS, DYNAMIC_TABLES, FILE_FORMATS, PIPES, MASKING_POLICIES, SESSION_POLICIES, PASSWORD_POLICIES, AUTHENTICATION_POLICIES, NOTEBOOKS), the role must have:
+For managing database-level objects (VIEWS, FUNCTIONS, PROCEDURES, TABLES, SEQUENCES, STAGES, STREAMS, TASKS, ALERTS, DYNAMIC_TABLES, FILE_FORMATS, PIPES, MASKING_POLICIES, ROW_ACCESS_POLICIES, TAGS, SESSION_POLICIES, PASSWORD_POLICIES, AUTHENTICATION_POLICIES, NOTEBOOKS), the role must have:
 - **USAGE** on the target schema
 - **CREATE** privileges for the specific object types being deployed (CREATE VIEW, CREATE FUNCTION, CREATE TABLE, etc.)
 - **ALTER** privileges on existing objects in the schema
@@ -520,7 +520,7 @@ For managing account-level objects, the role must have:
 ## DLSync Metadata Tables
 DLSync stores script metadata, deployment history, and logs in the database.
 DLSync will depend on these tables to track the changes and deployment history. If these tables are missing from the schema and database provided in the connection parameter, then DLSync will create these tables. 
-Please make sure the role provided in the connection has the necessary privileges to create tables in the schema.
+Please make sure the role provided in the connection has the necessary privileges to create tables in the schema. 
 
 **_N.B: Since DLSync uses these tables to track the changes, it is recommended not to delete or change these tables. It is also important not to change the schema of the connection. If DLSync is not able to find these tables in the schema, it will create them and assume it is running for the first time._**
 
diff --git a/example_scripts/main/example_db/MAIN_SCHEMA/ROW_ACCESS_POLICIES/CUSTOMER_ACCESS.SQL b/example_scripts/main/example_db/MAIN_SCHEMA/ROW_ACCESS_POLICIES/CUSTOMER_ACCESS.SQL
new file mode 100644
index 0000000..1112005
--- /dev/null
+++ b/example_scripts/main/example_db/MAIN_SCHEMA/ROW_ACCESS_POLICIES/CUSTOMER_ACCESS.SQL
@@ -0,0 +1,9 @@
+CREATE OR REPLACE ROW ACCESS POLICY ${EXAMPLE_DB}.${MAIN_SCHEMA}.CUSTOMER_ACCESS
+AS (customer_region VARCHAR)
+RETURNS BOOLEAN ->
+  CASE
+    WHEN CURRENT_ROLE() IN ('ADMIN', 'DATA_ADMIN') THEN TRUE
+    WHEN CURRENT_ROLE() = 'REGIONAL_ANALYST' AND customer_region = CURRENT_USER()
+      THEN TRUE
+    ELSE FALSE
+  END;
diff --git a/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java b/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java
index 7eb5c7d..f7c4a6d 100644
--- a/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java
+++ b/src/main/java/com/snowflake/dlsync/models/ScriptObjectType.java
@@ -24,6 +24,7 @@ public enum ScriptObjectType {
     WAREHOUSES("WAREHOUSE", ObjectLevel.ACCOUNT, false),
     NOTEBOOKS("NOTEBOOK", ObjectLevel.SCHEMA, false),
     TAGS("TAG", ObjectLevel.SCHEMA, false),
+    ROW_ACCESS_POLICIES("ROW ACCESS POLICY", ObjectLevel.SCHEMA, false),
 
     // Migration-enabled objects
     TABLES("TABLE", ObjectLevel.SCHEMA, true),
diff --git a/src/test/java/com/snowflake/dlsync/parser/SqlTokenizerTest.java b/src/test/java/com/snowflake/dlsync/parser/SqlTokenizerTest.java
index 63deb66..fa7e4eb 100644
--- a/src/test/java/com/snowflake/dlsync/parser/SqlTokenizerTest.java
+++ b/src/test/java/com/snowflake/dlsync/parser/SqlTokenizerTest.java
@@ -1039,5 +1039,39 @@ void parseSchemaScriptTypeAgentWithProfile() {
         assertEquals(content, script.getContent(), "Script content should match the input content");
     }
 
+    @Test
+    void parseSchemaScriptTypeRowAccessPolicy() {
+        String filePath = "db_scripts/db1/schema1/ROW_ACCESS_POLICIES/CUSTOMER_ACCESS.SQL";
+        String name = "CUSTOMER_ACCESS.SQL";
+        String scriptType = "ROW_ACCESS_POLICIES";
+        String content = "CREATE OR REPLACE ROW ACCESS POLICY db1.schema1.CUSTOMER_ACCESS AS (customer_region VARCHAR) RETURNS BOOLEAN -> CASE WHEN CURRENT_ROLE() IN ('ADMIN') THEN TRUE ELSE FALSE END;";
+
+        SchemaScript script = SqlTokenizer.parseSchemaScript(filePath, name, scriptType, content);
+
+        assertNotNull(script, "Scripts should not be null");
+        assertEquals("CUSTOMER_ACCESS", script.getObjectName(), "Object name should be CUSTOMER_ACCESS");
+        assertEquals("db1".toUpperCase(), script.getDatabaseName(), "Database name should be db1");
+        assertEquals("schema1".toUpperCase(), script.getSchemaName(), "Schema name should be schema1");
+        assertEquals(ScriptObjectType.ROW_ACCESS_POLICIES, script.getObjectType(), "Object type should be ROW_ACCESS_POLICIES");
+        assertEquals(content, script.getContent(), "Script content should match the input content");
+    }
+
+    @Test
+    void parseSchemaScriptTypeTag() {
+        String filePath = "db_scripts/db1/schema1/TAGS/COST_CENTER.SQL";
+        String name = "COST_CENTER.SQL";
+        String scriptType = "TAGS";
+        String content = "CREATE OR REPLACE TAG db1.schema1.COST_CENTER ALLOWED_VALUES 'finance', 'engineering', 'marketing' COMMENT = 'Tag for cost allocation';";
+
+        SchemaScript script = SqlTokenizer.parseSchemaScript(filePath, name, scriptType, content);
+
+        assertNotNull(script, "Scripts should not be null");
+        assertEquals("COST_CENTER", script.getObjectName(), "Object name should be COST_CENTER");
+        assertEquals("db1".toUpperCase(), script.getDatabaseName(), "Database name should be db1");
+        assertEquals("schema1".toUpperCase(), script.getSchemaName(), "Schema name should be schema1");
+        assertEquals(ScriptObjectType.TAGS, script.getObjectType(), "Object type should be TAGS");
+        assertEquals(content, script.getContent(), "Script content should match the input content");
+    }
+
 
 }
\ No newline at end of file