![]() ![]() Specifies the Liquibase Pro license key, if applicable. Specifies the password for the source database. Specifies the username for the source database. Specifies the source database for performing comparisons. Specifies the driver class name for the source database. Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro. Username to connect to the target database. Specifies the database to use when making comparisons to the source database. Specifies the driver class name for the target database. Specifies the path to the changelog to execute. For a full list, see Liquibase Parameters. The following table identifies some additional properties that can be specified in the liquibase.properties file. Instead, store them in a Secrets Management application or enter them in the CLI when you run a command. Warning: For security reasons, Liquibase strongly recommends that you do not include authentication information in your liquibase.properties file, such as the username, password, referenceUsername, and referencePassword properties. For more information about property formats, see Liquibase Database Tutorials. ![]() The values in a properties file must be specific to the database that it describes. See How to Apply Your Liquibase Pro License Key for more information. Specify your license key as the value, as the previous example shows.Add licenseKey: to the list of parameters.Using a text editor, open the Liquibase properties file.To activate a Liquibase Pro license key, perform the following steps: However, you can use quoted and unquoted values in the CLI. Note: The Liquibase properties file does not support quoted property values, such as driver: "". If placed your database's JDBC JAR file in a different directory, you must specify the path: classpath.//.jar. Tip: You do not need to specify a classpath for pre-installed drivers in the liquibase/internal/lib directory or for drivers you placed in the liquibase/lib directory. These tools require a Liquibase Pro license key. It is a best practice to include sensitive credentials in a Secrets Management tool like AWS Secrets Manager, CyberArk PAM Vault, or HashiCorp Vault. This example does not include authentication properties such as username, password, referenceUsername, and referencePassword. ReferenceUrl: aeioufakeke圓2aeioufakekey785463214Ĭlasspath. The following example liquibase.properties file works for an Oracle database: changelogFile. Note: The file can be named something other than liquibase.properties and reside in a different directory by using the -defaults-file attribute every time you run a Liquibase command.įor more information, see Working with Command Parameters. You can also manually create a new text file in your project Liquibase directory and name it liquibase.properties. You can easily create a new Liquibase project containing a liquibase.properties file by running the init project command. Liquibase comes preinstalled with example liquibase.properties files in the $LIQUIBASE_HOME/examples/ directories. This lets you avoid entering properties through your command line, saving you time and reducing errors.Īrguments that are entered at a command prompt override values that are specified in liquibase.properties. You can use a defaults file called liquibase.properties to store information that Liquibase needs to connect to a particular database, along with other properties that rarely change. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |