Liquibase

A Visual Studio Code extension that supports executing Liquibase commands without needing to use the command line.

You can also create and edit liquibase.properties files, which are used as a foundation for any command execution.

Getting started

You can also get a brief overview of the extension with our Walkthrough.

Creating a configuration

All commands that execute Liquibase need a liquibase.properties file. This file contains information about your database connection, including user name and password.

You can create a new configuration via the Liquibase: Create Liquibase Configuration command.

If you have pre-existing configurations, then you can use the Liquibase: Add existing liquibase.properties to the configuration... command to add this configuration to the workspace.

All the created and added configurations will be stored in the folder data/liquibase. You can change this folder with the setting liquibase.configurationPath.

NOTE: Do not add your configuration files and folder to your version control system. Instead, add them to your .gitignore. These files contain sensitive information.

You can later edit your configurations with the Liquibase: Edit existing Liquibase Configuration command. This command can be reached via the command palette or by opening the context menu in any .properties file.

Executing a command

All commands can be accessed from the "Liquibase" item in the status bar.

You can also access all commands by using the the command palette. It can be accessed with the keyboard shortcut Ctrl + Shift + P (macOS Cmd + Shift + P).

If you execute any command, you notice a general pattern of inputs. You will be always asked the following steps in this order:

1. Select the configuration of your database. This is needed for Liquibase to know how to access your database. Liquibase can also extract automatically other parameters from it.
2. Select the changelog. This is used for knowing what to execute. Not all commands require this option. If you call a command from a context menu, the changelog will be set to the file where you opened the context menu.
3. Select the contexts. Some commands allow you to filter the changelogs by contexts. See "Executing commands with and without contexts" for more details.
4. Any additional options you need to give before you can execute the command.

Some commands are accessible from the context menu. The context menu is available for all xml, json, yaml, yml and sql files, because those are the languages where you can write Liquibase changelogs. All commands are found in the "Liquibase" sub menu. When executing a command from the context menu, it will use the current file as your changelog.

Supported Liquibase Commands

Currently, the following Liquibase commands are supported:

Tip: The link on the command itself will lead you to the Liquibase documentation. This will give you a better understanding of the technical details of each command.

The name in brackets is the real name of the command given by Liquibase. This will be used, if the display name is different than the original name.

• Compare two databases (diff)
• Clear the checksums of all changelogs in the database
• Create Tag
• Drop-all
• Generate Changelog
• Generate database documentation (db-doc) - more details below
• Generate SQL File for incoming changes
• List all deployed changesets (history)
• List the not deployed changesets (status)
• Mark not deployed changelogs as executed (changelog-sync)
• Rollback to Tag
• Tag Exists
• Update - Default Keyboard shortcut: Ctrl + Alt + U (macOS Cmd + Alt + U)
• Unexpected Changesets
• Validate

Every command that needs a changelog file, can be executed by right clicking on or in any changelog file. These commands that are possible to open in a context menu contains Update, Validate, Status and many more.

Generate database documentation / Getting an overview about your database

Sometimes, you want to have an overview about your whole database. For this, we have a useful command in the status bar labeled "Overview".

This will create an HTML report with a lot of useful information regarding your database and the changelogs.

You can see information about the current table structure, including columns and indexes.

Also, you can see the authors of every changeset referenced into the root changelog and any pending changes.

The overview command will be creating some HTML files in your OS temporary directory (e.g. Windows %LOCALAPPDATA%\temp\liquibase-overview). You can view the results by opening the index.html file in any web browser. The command will also open this file for you automatically once it is finished.

If you want to control the storage location of the overview output, you can use the Liquibase: Generate database documentation (db-doc) command. This will produce the same result as the overview item in the status bar.

Executing commands with and without contexts

Many liquibase commands can be executed with a context. After a connection and a changelog file was selected, you might be prompted with a context selection. There you have different options:

• Use any of the recently loaded contexts: This will give you all contexts that were recently loaded by "Load all contexts from the changelog file". You should use this option, if you want to use contexts and these have not changed from any recently loaded contexts. This option is only visible, if cached contexts are there.
• Load all contexts from the changelog file: This will parse and read all changelog files based on your root changelog file. Anytime you load new contexts, the old ones for this connection will be discarded. This option should be used, if you never have loaded your contexts before or your contexts have changed from any recently loaded context and you want to execute the query with contexts.
• Do not use any contexts: This will execute all changesets that does not have any context given. Every changeset with a context will be ignored. This option should be used, if you are certain that you don't need any context(s) to execute the command.

Both "Load all contexts from the changelog file" and "Use any of the recently loaded contexts" will not use any contexts for your command, if there is no context selected.

The recently loaded contexts are saved per database connection. That means, if you have three connections, then you have three sections of the contexts. For more information regarding caching, see the caching section.

Converting changelogs from one liquibase format to another format

With the two commands Liquibase: Converts a file from one liquibase format to another and Liquibase: Converts a folder from one liquibase format to another, you can convert changelogs from one format to another.

NOTE: It is very important, that you check to produced results by the command. We do not guarantee the completeness and correctness of the files.

Restrictions:

• Files with include / includeAll will not be transformed to the new format, due to the limitations of Liquibase. But all path given in the file attribute in the include elements will be transformed to a new path, if the old path was transformed as well.

• When transforming to YAML or JSON files with preConditions will produce invalid results (Liquibase Issue #4379)

Caching

During the command execution, we will save the following values for every liquibase.properties file:

• last loaded contexts from any context command
• the five last selected changelogs

You can see the cache file with the Liquibase: Cache: Open the file with the recently loaded elements command.

You can remove any values from the cache with the Liquibase: Cache: Remove any values from the recently loaded elements command. A manual editing of the cache is not recommended.

View logs

This extension write to the output. It can be viewed by executing the command Output: Focus on Output View and then selecting the channel "Liquibase".

Logs will be also written to a log folder on your OS. You can reach the log folder by executing the command Developer: Open Extension Logs Folder and then navigating to the liquibase folder.