Page Comparison

Steps to test

...

Liquibase change log

1. Run a new postgres instance container on your local machine

...

2. Checkout honolulu branch and cd to "cps-ri"

3. Run "status" liquibase script to observe that your database is not up to date and see the list of all changes set that need to be applied for honolulu

...

5. Run "status" liquibase script to validate that your db is now up to date for honolulu (Run step 3 command)

6. Check out master branch (or the branch having your liquibase fix) and cd to "cps-ri"

7. Run "status" liquibase script to see the list of all change sets that need to be applied for istambul (if any) (Run step 3 command)

...

8. Run "update" liquibase script to apply all pending changes set and bring your database to istanbul version (Run step 4 command) 9. Run "status" liquibase script to validate that your db is now up to date for istambul (Run step 3 command)

Steps to test Liquibase Rollback

9. In case the latest updates needs to be rolled back, the below options could be used:

• liquibase.rollbackCount - reverts a specified number of changesets sequentially, starting with the most recent changes and working backward until the value specified is reached :

  • 
    

    Code Block
    mvn clean compile org.liquibase:liquibase-maven-plugin:3.8.7:rollback -Dliquibase.url=jdbc:postgresql://localhost:5432/cpsdb -Dliquibase.username=cps -Dliquibase.password=cps -Dliquibase.changeLogFile=changelog/changelog-master.yaml -Dliquibase.rollbackCount=x

    
    

• liquibase.rollbackTag - reverts all changes that were made to the database after the specified tag:

  • 
    

    Code Block
    mvn clean compile org.liquibase:liquibase-maven-plugin:3.8.7:rollback -Dliquibase.url=jdbc:postgresql://localhost:5432/cpsdb -Dliquibase.username=cps -Dliquibase.password=cps -Dliquibase.changeLogFile=changelog/changelog-master.yaml -Dliquibase.rollbackTag=<liquibase_tag_for_changesets_to_be_rolled_back>

    
    

• liquibase.rollbackDate - reverts all changes made to your database from today's date to the date and time you specify.

  • 
    

    Code Block
    mvn clean compile org.liquibase:liquibase-maven-plugin:3.8.7:rollback -Dliquibase.url=jdbc:postgresql://localhost:5432/cpsdb -Dliquibase.username=cps -Dliquibase.password=cps -Dliquibase.changeLogFile=changelog/changelog-master.yaml -Dliquibase.rollbackDate=2020-11-26

    
    

See also DB Schema Changes (Liquibase Change Logs)

Steps to create checksum for yang-resource

1. Build locally using

/onap/cps/cps-application$ mvn clean install -Pcps-ncmp-docker -DskiptTests=true
then run 
/onap/cps/docker-compose$ VERSION=latest DB_USERNAME=cps DB_PASSWORD=cps docker-compose up -d

2. Run to create new dataspace (if needed)

curl --location --request POST 'http://localhost:8883/cps/api/v1/dataspaces?dataspace-name=NSODemo' \
--header 'Authorization: Basic Y3BzdXNlcjpjcHNyMGNrcyE='

3. Run to insert a yang resource.

     NOTE: Remove all escape characters from file, check attached file for reference.

curl --location --request POST 'http://localhost:8883/cps/api/v1/dataspaces/NSODemo/schema-sets' \
--header 'Authorization: Basic Y3BzdXNlcjpjcHNyMGNrcyE=' \
--form 'file=@"****path-to-yang-file****"' \                      // insert your yang file path here
--form 'schema-set-name="dmi-registry@2021-05-20.yang"'

4. login to postgres and check the entry in table to verify checksum

psql -h localhost -p 5432 -U cps -d cpsdb

select * from yang_resource where name like '%dmi%'; //replace dmi with your names

Note about rollback

See:

* https://docs.liquibase.com/concepts/bestpractices.html in "Always think about rollback" section
* https://docs.liquibase.com/workflows/liquibase-community/using-rollback.html