public class LiquibaseUpdatePlugin
This script is the second of a pair. When called from the RunLiquibaseUPdates.sh, it follows a call to CheckDBVersionPlugin. The latter verifies the db is a candidate for liquibase updates (ie, it contains tables/columns indicating the version is appropriate for the current liquibase changesets).
This plugin assumes a ParameterCache is used for the db configuration variables. The parameter cache is added to the command line prior to the plugin name, as below:
/tassel-5-standalone/run_pipeline.pl ${fullXmx} -debug -configParameters $DATA_PATH/$dbConfigFile -CheckDBVersionPlugin -outputDir $OUTPUT_PATH -endPlugin -LiquibaseUpdatePlugin -outputDir $OUTPUT_PATH -endPlugin
CheckDBVersionPlugin writes one of 2 files: either run_yes.txt or run_no.txt They are written to the same output directory that is mounted here. If run_yes.txt is not present, this script will abort with an error message indicating the db cannot be updated.
LiquibaseUpdatePlugin runs liquibase with a jdbc driver, determined based on the DBtype parameter from the config file. It is assumed this script is run from within a PHG liquibase docker. The correct jdbc driver (sqlite or postgres) is selected based on the DBtype parameter present in the config file.
This method is run for both the "changeLogSync" command (which marks all changes logs as "ran"), and the "update" command, which executes each changeset from the changelogs files.
public LiquibaseUpdatePlugin(@Nullable
java.awt.Frame parentFrame,
boolean isInteractive)
This script is the second of a pair. When called from the RunLiquibaseUPdates.sh, it follows a call to CheckDBVersionPlugin. The latter verifies the db is a candidate for liquibase updates (ie, it contains tables/columns indicating the version is appropriate for the current liquibase changesets).
This plugin assumes a ParameterCache is used for the db configuration variables. The parameter cache is added to the command line prior to the plugin name, as below:
/tassel-5-standalone/run_pipeline.pl ${fullXmx} -debug -configParameters $DATA_PATH/$dbConfigFile -CheckDBVersionPlugin -outputDir $OUTPUT_PATH -endPlugin -LiquibaseUpdatePlugin -outputDir $OUTPUT_PATH -endPlugin
CheckDBVersionPlugin writes one of 2 files: either run_yes.txt or run_no.txt They are written to the same output directory that is mounted here. If run_yes.txt is not present, this script will abort with an error message indicating the db cannot be updated.
LiquibaseUpdatePlugin runs liquibase with a jdbc driver, determined based on the DBtype parameter from the config file. It is assumed this script is run from within a PHG liquibase docker. The correct jdbc driver (sqlite or postgres) is selected based on the DBtype parameter present in the config file.
This method is run for both the "changeLogSync" command (which marks all changes logs as "ran"), and the "update" command, which executes each changeset from the changelogs files.
@Nullable
public net.maizegenetics.plugindef.DataSet processData(@Nullable
net.maizegenetics.plugindef.DataSet input)
@Nullable public javax.swing.ImageIcon getIcon()
@NotNull public java.lang.String getButtonName()
@NotNull public java.lang.String getToolTipText()
@NotNull public java.lang.String outputDir()
Directory path to write any liquibase output files.
@NotNull public LiquibaseUpdatePlugin outputDir(@NotNull java.lang.String value)
Set Output Directory. Directory path to write any liquibase output files.
value - Output Directory@NotNull public java.lang.String command()
Command for liquibase to execute: must be update or changeLogSync, defaults to update.
@NotNull public LiquibaseUpdatePlugin command(@NotNull java.lang.String value)
Set Liquibase command. Command for liquibase to execute: must be update or changeLogSync, defaults to update.
value - Liquibase command