You're viewing an older version of this GitHub Action. Do you want to see the latest version instead?
GitHub Action
Liquibase Github Action
v1
Official Github Action to run Liquibase in your pipeline.
Basic Update
steps:
- uses: actions/checkout@v2
- uses: liquibase/liquibase-github-action@v1
with:
operation: 'update'
classpath: 'example/changelogs'
changeLogFile: 'samplechangelog.h2.sql'
username: ${{ secrets.USERNAME }}
password: ${{ secrets.PASSWORD }}
url: ${{ secrets.URL }}
Optional Parameter Example:
steps:
- uses: actions/checkout@v2
- uses: liquibase/liquibase-github-action@v1
with:
operation: 'updateCount'
classpath: 'example/changelogs'
changeLogFile: 'samplechangelog.h2.sql'
username: ${{ secrets.USERNAME }}
password: ${{ secrets.PASSWORD }}
url: ${{ secrets.URL }}
count: 2
operation
, username
, password
, and url
are required for every use.
The operation
input expects one of the following:
- update
- updateCount
- tag
- updateToTag
- rollback
- rollbackCount
- rollbackToDate
- updateSQL
- futureRollbackSQL
- status
- history
- diff
classpath
, changeLogFile
, count
, tag
, date
, and referenceUrl
are optional inputs that may be required by some operations. The following operations have the subsequent required inputs:
- classpath
- changeLogFile
- count
- tag
- classpath
- changeLogFile
- tag
- classpath
- changeLogFile
- tag
- classpath
- changeLogFile
- count
- classpath
- changeLogFile
- date
- changeLogFile
- classpath
- changeLogFile
- classpath
- changeLogFile
- referenceUrl
It is a good practice to protect your database credentials with Github Secrets
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing!