Content Comparison

...

Create a branch for the VDB name in the denodo-vcs repo using the the GitHub web UI or the following command if you have the repo on your machine.

export VDBBRANCH_NAME=VDB_NAME-DENODO_MAJOR_VERSION
git switch --orphan $VDB$BRANCH_NAME
git commit --allow-empty -m "initial commit for $VDB$BRANCH_NAME"
git push

Migrating VDB’s Into Their Own Branch

...

1. Commit and push the whole VDB

2. Export the VDB, be sure to uncheck Enter Single User Mode for Import

3. Delete the local repository for the VDB from the dev VDP server

   Code Block
   rm -rf /opt/denodo/work/vdp/repository/$VDB_NAME

4. Create an empty branch in denodo-vcs that matches the VDB name

   Code Block
   export VDBBRANCH_NAME=VDB_NAME-DENODO_MAJOR_VERSION git switch --orphan $VDB$BRANCH_NAME git commit --allow-empty -m "initial commit for $VDB$BRANCH_NAME" git push

5. Update the VCS configuration for the VDB to use the new branch (you’ll need need the tufts_denodo token from CyberArk)
   

   

6. Perform a Pull for the VDB
   

   

7. Run the VQL script from the VDB export, be sure to remove ENTER SINGLE USER MODE and EXIT SINGLE USER MODE, these commands don't work properly and cause the whole VDP server to freeze and require a restart.

8. Create a commit for the VDB

9. Push the VDB

...