-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #9 from liquibase/JIRA-2
add third repo
- Loading branch information
Showing
7 changed files
with
305 additions
and
177 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
########## LIQUIBASE FLOWFILE ########## | ||
########## learn more http://docs.liquibase.com/flow ########## | ||
|
||
## Note: Any command which fails in any stage below result in the command stopping, and endStage being run. | ||
## A flow file can have one or more stages, each with multiple "actions", | ||
## or your flow file can have multiple stages with fewer actions in each stage. | ||
|
||
## Call this flow using: liquibase flow --flow-file=flowfiles/liquibase-deploy.flowfile.yaml | ||
|
||
stages: | ||
|
||
Checks-Changelog: | ||
actions: | ||
- type: liquibase | ||
command: checks run | ||
cmdArgs: { | ||
checks-scope: changelog, | ||
checks-settings-file: "policychecks/liquibase.checks-settings.conf", | ||
auto-update: "ON", | ||
changeset-filter: "pending" | ||
} | ||
globalArgs: { | ||
reports-name: "checks-report-deploy-changelog.html" | ||
} | ||
|
||
Status: | ||
actions: | ||
- type: liquibase | ||
command: status | ||
cmdArgs: {verbose: true} | ||
|
||
Update-SQL: | ||
actions: | ||
- type: liquibase | ||
command: update-sql | ||
|
||
Update: | ||
actions: | ||
- type: liquibase | ||
command: update | ||
|
||
Checks-Database: | ||
actions: | ||
- type: liquibase | ||
command: checks run | ||
cmdArgs: { | ||
checks-scope: database, | ||
checks-settings-file: "policychecks/liquibase.checks-settings.conf", | ||
auto-update: "ON" | ||
} | ||
globalArgs: { | ||
reports-name: "checks-report-deploy-database.html" | ||
} | ||
|
||
## The endStage ALWAYS RUNS. | ||
## So put actions here which you desire to perform whether previous stages' actions succeed or fail. | ||
## If you do not want any actions to ALWAYS RUN, simply delete the endStage from your flow file. | ||
|
||
endStage: | ||
actions: | ||
- type: liquibase | ||
command: history |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
########## LIQUIBASE FLOWFILE ########## | ||
########## learn more http://docs.liquibase.com/flow ########## | ||
|
||
## Note: Any command which fails in any stage below result in the command stopping, and endStage being run. | ||
## A flow file can have one or more stages, each with multiple "actions", | ||
## or your flow file can have multiple stages with fewer actions in each stage. | ||
|
||
## Call this flow using: liquibase flow --flow-file=flowfiles/liquibase-postmerge.flowfile.yaml | ||
|
||
stages: | ||
|
||
Status: | ||
actions: | ||
- type: liquibase | ||
command: status | ||
cmdArgs: {verbose: true} | ||
|
||
Update-SQL: | ||
actions: | ||
- type: liquibase | ||
command: update-sql | ||
|
||
Update: | ||
actions: | ||
- type: liquibase | ||
command: update | ||
|
||
PostDeploy-Checks: | ||
actions: | ||
- type: liquibase | ||
command: checks run | ||
cmdArgs: { | ||
checks-scope: database, | ||
checks-settings-file: "policychecks/liquibase.checks-settings.conf", | ||
auto-update: "ON", | ||
changeset-filter: "pending" | ||
} | ||
globalArgs: { | ||
reports-name: "checks-report-database.html" | ||
} | ||
|
||
## The endStage ALWAYS RUNS. | ||
## So put actions here which you desire to perform whether previous stages' actions succeed or fail. | ||
## If you do not want any actions to ALWAYS RUN, simply delete the endStage from your flow file. | ||
|
||
endStage: | ||
actions: | ||
- type: liquibase | ||
command: history |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
########## LIQUIBASE FLOWFILE ########## | ||
########## learn more http://docs.liquibase.com/flow ########## | ||
|
||
## Note: Any command which fails in any stage below result in the command stopping, and endStage being run. | ||
## A flow file can have one or more stages, each with multiple "actions", | ||
## or your flow file can have multiple stages with fewer actions in each stage. | ||
|
||
## Call this flow using: liquibase flow --flow-file=flowfiles/liquibase-premerge.flowfile.yaml | ||
|
||
stages: | ||
|
||
PreMerge-Checks: | ||
actions: | ||
- type: liquibase | ||
command: checks run | ||
cmdArgs: { checks-scope: changelog, | ||
checks-settings-file: "policychecks/liquibase.checks-settings.conf", | ||
auto-update: "ON", | ||
changeset-filter: "pending" | ||
} | ||
globalArgs: { | ||
reports-name: "checks-report-premerge.html" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
########## LIQUIBASE FLOWFILE ########## | ||
########## learn more http://docs.liquibase.com/flow ########## | ||
|
||
## Note: Any command which fails in any stage below result in the command stopping, and endStage being run. | ||
## A flow file can have one or more stages, each with multiple "actions", | ||
## or your flow file can have multiple stages with fewer actions in each stage. | ||
|
||
## Call this flow using: liquibase flow --flow-file=flowfiles/liquibase-rollback.flowfile.yaml | ||
|
||
stages: | ||
|
||
Rollback-SQL: | ||
actions: | ||
- type: liquibase | ||
command: rollback-one-update-sql | ||
|
||
Rollback: | ||
actions: | ||
- type: liquibase | ||
command: rollback-one-update | ||
cmdArgs: { | ||
force: true | ||
} | ||
|
||
## The endStage ALWAYS RUNS. | ||
## So put actions here which you desire to perform whether previous stages' actions succeed or fail. | ||
## If you do not want any actions to ALWAYS RUN, simply delete the endStage from your flow file. | ||
|
||
endStage: | ||
actions: | ||
- type: liquibase | ||
command: history |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.